Automated Event Processing Computing Platform for Handling and Enriching Blockchain Data

ABSTRACT

Methods and systems for using block chain technology to verify transaction data are described herein. A computing platform may receive data about events related to transactions, personal or corporate information, supply chains, and other relevant information about a person or corporate entity. The event information may be received, aggregated, and processed to determine metadata about the person or corporate entity. The metadata may indicate, for example, a trustworthiness of the person or corporate entity for various purposes. Such event information and/or metadata may be stored as transactions in a block chain that may be accessible by counterparties to a potential transaction involving the person or corporate entity. The automated event processing computing platform may further use automated techniques to implement smart transactions between the person/entity and counterparty based on the trust metadata.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to patentapplication Ser. No. 15/834,305 entitled “Automated Event ProcessingComputing Platform for Handling and Enriching Blockchain Data” and filedon Dec. 7, 2017, which is incorporated by reference in its entirety.

FIELD

Aspects described herein generally relate to electrical computers anddigital processing systems, multicomputer data transferring, anddistributed data processing. In particular, one or more aspects of thedisclosure relate to digital processing systems that create and maintainblock chain data structures.

BACKGROUND

Block chain systems are increasingly used to record transaction data viadistributed computing devices. Block chains beneficially allow secure,distributed storage of event and transaction data that is verifiable andresistant to unauthorized usage. But existing systems for transactingwith others via a block chain or otherwise do not provide sufficientinformation about the transaction counterparty or counterparties. Forexample, in transactions using some cryptocurrencies, a counterparty maybe anonymous or pseudonymous. This may prevent or limit the adoption ofcryptocurrencies for many common use cases. Additionally, lack ofsufficient information about a potential counterparty may limit theability to engage in transactions of assets via currencies or any otherassets.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify required or critical elements or to delineate the scope ofthe claims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein aredirected towards effective, efficient, scalable, and convenienttechnical solutions for using block chain technology to verifytransaction data.

According to one or more aspects described herein, a computing platformcomprising one or more processors, memory, and a network interfacereceives, via the network interface, information identifying a user;retrieves, from one or more blocks of a blockchain stored in the memory,a plurality of historical information associated with the user;calculates, based on the historical information associated with theuser, a trust level associated with the user; executes a function storedon the blockchain, wherein the function comprises conditional logicbased on the trust level associated with the user; generates a new blockcomprising a data structure including data modified by the executedfunction; and transmits the new block to a plurality of nodes thatmaintain the blockchain.

In some cases, the computing platform, prior to the receiving ofinformation identifying the user, receives user authorization to accessrecords maintained by one or more systems that record events about theuser; and receives, from the one or more systems that record eventsabout the users, the historical information.

In some cases, the computing platform determines, based on theinformation identifying the user, a blockchain identifier associatedwith the user, wherein the new block comprises the blockchainidentifier.

The computing platform may execute the conditional logic if the trustlevel is above a threshold. Additionally or alternatively, the computingplatform may execute the conditional logic to adjust a value based onthe trust level. Prior to the executing of the function, the computingplatform may receive, from the user, a payment of a token associatedwith the blockchain.

According to some aspects, the memory of the computing platformcomprises a plurality of user blockchains associated with a respectiveplurality of users, and the computing platform generates, for a mainblockchain that is separate from the plurality of user blockchains, asecond new block comprising the trust level; and transmits the secondnew block to the plurality of nodes that maintain the blockchain.

According to some aspects, generating the new block causes the computingplatform to receive tokens associated with the blockchain.

According to some aspects, the computing platform generates, based onthe historical information associated with the user and on historicalinformation associated with other users, aggregated marketing data;receives, from a third party computing device, a request for theaggregated marketing data; and provides, to the third party computingdevice, the aggregated marketing data in exchange for tokens associatedwith the blockchain.

In some cases, the historical information comprises information abouttransactions with other users or entities, locations of thetransactions, and amounts of the transactions. Additionally oralternatively, the historical information further comprises one or moreof user demographic information, user credit report information, andinformation about user assets.

In some cases, the executed function initializes a second function forreceiving a bid on a loan to the user.

According to one or more further aspects described herein, a computingplatform comprising one or more processors, memory, and a networkinterface receives, via the network interface, information about asupply chain associated with a first corporate entity; retrieves, fromone or more blockchains stored in the memory, information about aplurality of corporate entities associated with the supply chain;calculates, based on the information about the supply chain and on theinformation for the plurality of corporate entities, a trust levelassociated with the first corporate entity; executes a function storedon the blockchain, wherein the function comprises conditional logicbased on the trust level associated with the first corporate entity;generates a new block comprising a data structure including datamodified by the executed function; and transmits the new block to aplurality of nodes that maintain the one or more blockchains.

In some cases, prior to the receiving of the information about thesupply chain, the computing platform receives credentials for accessingan interface of one or more computing devices associated with the firstcorporate entity.

According to some aspects, the information about the plurality ofcorporate entities associated with the supply chain further comprisesinformation about supply chains respectively associated with theplurality of corporate entities.

In some cases, prior to the calculating of the trust level, thecomputing platform compares the information about the supply chainsrespectively associated with the plurality of corporate entities to theinformation about the supply chain associated with the first corporateentity, wherein the trust level is based on the comparison.

In some cases, the information for the plurality of corporate entitiesincludes respective countries of incorporation for the plurality ofcorporate entities.

According to some aspects, the computing platform generates a second newblock comprising the trust level; and transmits the second new block tothe plurality of nodes that maintain the one or more blockchains.Additionally or alternatively, the one or more blockchains comprise aplurality of corporate entity blockchains respectively associated withthe plurality of corporate entities, wherein the second new block is fora main blockchain that is separate from the plurality of corporateentity blockchains.

According to some aspects, the conditional logic only executes if thetrust level is above a threshold. Additionally or alternatively, theconditional logic adjusts a value based on the trust level.

In some cases, prior to the executing of the function, the computingplatform receives, from the first corporate entity, a payment of a tokenassociated with the one or more blockchains.

According to some aspects, generating the new block causes the computingplatform to receive tokens associated with the blockchain.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative example of centralized computer system inaccordance with one or more illustrative aspects described herein.

FIG. 2 depicts an illustrative example of decentralized P2P computersystem that may be used in accordance with one or more illustrativeaspects described herein.

FIG. 3A depicts an illustrative example of a full node computing devicethat may be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3B depicts an illustrative example of a lightweight node computingdevice that may be used in accordance with one or more illustrativeaspects described herein.

FIG. 4 depicts an illustrative operating environment for implementingaspects described herein.

FIGS. 5A, 5B, 5C, 5D, 5E, and 5F illustrate an example process that maybe implemented by a computing platform in accordance with one or moreaspects described herein.

FIGS. 6A and 6B illustrate example user interfaces in accordance withone or more illustrative aspects described herein.

FIG. 7 depicts an illustrative operating environment for implementingaspects described herein.

FIGS. 8A, 8B, 8C, 8D, and 8E illustrate an example process that may beimplemented by a computing platform in accordance with one or moreaspects described herein.

FIG. 9 illustrates an example process that may be implemented by acomputing platform in accordance with one or more aspects describedherein.

FIG. 10 illustrates an example process that may be implemented by acomputing platform in accordance with one or more aspects describedherein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards using block chaintechnology to verify transaction data (e.g., by obtaining informationabout the trustworthiness of counterparties to a potential transaction).An automated event processing computing platform may receive data orother information about events related to financial transactions,personal and/or corporate information, supply chains, and other relevantinformation about a person or corporate entity. The event informationmay be received, aggregated, and processed to determine metadata aboutthe person or corporate entity. The metadata may indicate, for example,a trustworthiness of the person or corporate entity for variouspurposes. Such event information and/or metadata may be stored astransactions in a block chain that may be accessible by counterpartiesto a potential transaction involving the person or corporate entity. Theautomated event processing computing platform may further use automatedtechniques to implement smart transactions between the person/entity andcounterparty based on the trust metadata. The automated event processingcomputing platform may further provide services related to theinformation on the block chain, such as transaction verification,analysis of the metadata, and analysis of the event data to generatemarketing, ad targeting, or other analytics information.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

The disclosure provided herein is described, at least in part, inrelation to a decentralized peer-to-peer (e.g., P2P) system specializedfor the purpose of managing one or more blockchains. The decentralizedP2P system may comprise computing devices that are distributed inmultiple locations across a geographical area as opposed to a singlelocation such as a business or company. The computing devices formingthe decentralized P2P system may operate with each other to manage ablockchain, which may be a data structure used to store informationrelated to the decentralized P2P system. More specifically, theblockchain may be a chronological linkage of data elements (e.g.,blocks) which store data records relating to the decentralized computingsystem.

A user may access the decentralized P2P system through a specialized“wallet” that serves to uniquely identify the user and enable the userto perform functions related to the decentralized P2P network. Throughthe wallet, the user may be able to hold tokens, funds, or any otherasset associated with the decentralized P2P system. Furthermore, theuser may be able to use the wallet to request performance ofnetwork-specific functions related to the decentralized P2P system suchas fund, token, and/or asset transfers. The various computing devicesforming the decentralized P2P computing system may operate as a team toperform network-specific functions requested by the user. In performingthe network-specific functions, the various computing devices mayproduce blocks that store the data generated during the performance ofthe network-specific functions and may add the blocks to the blockchain.After the block has been added to the blockchain, the wallet associatedwith the user may indicate that the requested network-specific functionhas been performed.

For example, a user may have a wallet which reflects that the user hasfive tokens associated with the decentralized P2P system. The user mayprovide a request to the decentralized P2P system to transfer the fivetokens to a friend who also has a wallet. The various computing devicesforming the decentralized P2P computing system may perform the requestand transfer the five tokens from the wallet of the user to the walletof the friend. In doing so, a block may be created by the variouscomputing devices of the decentralized P2P computing system. The blockmay store data indicating that the five tokens were transferred from thewallet of the user to the wallet of the friend. The various computingdevices may add the block to the blockchain. At such a point, the walletof the user may reflect the transfer of the five tokens to the wallet ofthe friend, and may indicate a balance of zero. The wallet of thefriend, however, may also reflect the transfer of the five tokens andmay have a balance of five tokens.

In more detail, the decentralized P2P system may be specialized for thepurpose of managing one or more distributed ledgers, such as privateblockchain(s) and/or public blockchain(s), through the implementation ofdigital cryptographic hash functions, consensus algorithms, digitalsignature information, and network-specific protocols and commands. Thedecentralized P2P system (e.g., decentralized system) may be comprisedof decentralized system infrastructure consisting of a pluralitycomputing devices, either of a heterogeneous or homogenous type, whichserve as network nodes (e.g., full nodes and/or lightweight nodes) tocreate and sustain a decentralized P2P network (e.g., decentralizednetwork). Each of the full network nodes may have a complete replica orcopy of a blockchain stored in memory and may operate in concert, basedon the digital cryptographic hash functions, consensus algorithms,digital signature information, and network-specific protocols, toexecute network functions and/or maintain inter-nodal agreement as tothe state of the blockchain. Each of the lightweight network nodes mayhave at least a partial replica or copy of the blockchain stored inmemory and may request performance of network functions through theusage of digital signature information, hash functions, and networkcommands. In executing network functions of the decentralized network,such as balance sheet transactions and smart contract operations, atleast a portion of the full nodes forming the decentralized network mayexecute the one or more cryptographic hash functions, consensusalgorithms, and network-specific protocols to register a requestednetwork function on the blockchain. In some instances, a plurality ofnetwork function requests may be broadcasted across at least a portionof the full nodes of the decentralized network, aggregated throughexecution of the one or more digital cryptographic hash functions, andvalidated by performance of the one or more consensus algorithms togenerate a single work unit (e.g., block), which may be added in atime-based, chronological manner to the blockchain through performanceof network-specific protocols.

While in practice the term “blockchain” may hold a variety ofcontextually derived meanings, the term blockchain, as used herein,refers to a concatenation of sequentially dependent data elements (e.g.,blocks) acting as a data ledger that stores records relating to adecentralized computing system. Such data records may be related tothose used by a particular entity or enterprise, such as a financialinstitution, and/or may be associated with a particular applicationand/or use case including, but not limited to, cryptocurrency, digitalcontent storage and delivery, entity authentication and authorization,digital identity, marketplace creation and operation, internet of things(e.g., IoT), prediction platforms, election voting, medical records,currency exchange and remittance, P2P transfers, ride sharing, gaming,trading platforms, and real estate, precious metal, and work of artregistration and transference, among others. A “private blockchain” mayrefer to a blockchain of a decentralized private system in which onlyauthorized computing devices are permitted to act as nodes in adecentralized private network and have access to the private blockchain.In some instances, the private blockchain may be viewable and/oraccessible by authorized computing devices that are not participating asnodes within the decentralized private network, but still have propercredentials. A “public blockchain” may refer to a blockchain of adecentralized public system in which any computing devices may bepermitted to act as nodes in a decentralized public network and haveaccess to the public blockchain. In some instances, the publicblockchain may be viewable and/or accessible by computing devices thatare not participating as nodes within the decentralized public network.

Further, a “full node” or “full node computing device,” as used herein,may describe a computing device in a decentralized system that operatesto create and maintain a decentralized network, execute requestednetwork functions, and maintain inter-nodal agreement as to the state ofthe blockchain. In order to perform such responsibilities, a computingdevice operating as a full node in the decentralized system may have acomplete replica or copy of the blockchain stored in memory, as well asexecutable instructions for the execution of hash functions, consensusalgorithms, digital signature information, network protocols, andnetwork commands. A “lightweight node,” “light node,” “lightweight nodecomputing device,” or “light node computing device” may refer to acomputing device in a decentralized system, which operates to requestperformance of network functions (e.g., balance sheet transactions,smart contract operations, and the like) within a decentralized networkbut without the capacity to execute requested network functions andmaintain inter-nodal agreement as to the state of the blockchain. Assuch, a computing device operating as a lightweight node in thedecentralized system may have a partial replica or copy of theblockchain. In some instances, network functions requested bylightweight nodes to be performed by the decentralized network may alsobe able to be requested by full nodes in the decentralized system.

“Network functions” and/or “network-specific functions,” as describedherein, may relate to functions that can be performed by nodes of adecentralized P2P network. In some arrangements, the data generated inperforming network-specific functions may or may not be stored on ablockchain associated with the decentralized P2P network. Examples ofnetwork functions may include “smart contract operations” and “balancesheet transaction.” A smart contract operation, as used herein, maydescribe one or more operations associated with a “smart contract,”which may be one or more algorithms and/or programs stored on ablockchain and identified by one or more wallets and/or public keyswithin a decentralized P2P network. In performing a smart contractoperation, each full node computing device within a decentralized P2Pnetwork may identify a block within a blockchain comprising the smartcontract and, responsive to identifying the block associated with thesmart contract, may execute the one or more algorithms and/or programsof the smart contract. A balance sheet transaction may describe one ormore changes to data holdings associated with one or more nodes within adecentralized network.

In one or more aspects of the disclosure, a “digital cryptographic hashfunction,” as used herein, may refer to any function which takes aninput string of characters (e.g., message), either of a fixed length ornon-fixed length, and returns an output string of characters (e.g.,hash, hash value, message digest, digital fingerprint, digest, and/orchecksum) of a fixed length. Examples of digital cryptographic hashfunctions may include BLAKE (e.g., BLAKE-256, BLAKE-512, and the like),MD (e.g., MD2, MD4, MD5, and the like), Scrypt, SHA (e.g., SHA-1,SHA-256, SHA-512, and the like), Skein, Spectral Hash, SWIFT, Tiger, andso on. A “consensus algorithm,” as used herein and as described infurther detail below, may refer to one or more algorithms for achievingagreement on one or more data values among nodes in a decentralizednetwork. Examples of consensus algorithms may include proof of work(e.g., PoW), proof of stake (e.g., PoS), delegated proof of stake (e.g.,DPoS), practical byzantine fault tolerance algorithm (e.g., PBFT), andso on. Furthermore, “digital signature information” may refer to one ormore private/public key pairs and digital signature algorithms that areused to digitally sign a message and/or network function request for thepurposes of identity and/or authenticity verification. Examples ofdigital signature algorithms which use private/public key pairscontemplated herein may include public key infrastructure (PKI),Rivest-Shamir-Adleman signature schemes (e.g., RSA), digital signaturealgorithm (e.g., DSA), Edwards-curve digital signature algorithm, andthe like. A “wallet,” as used herein, may refer to one or more dataand/or software elements (e.g., digital cryptographic hash functions,digital signature information, and network-specific commands) that allowa node in a decentralized P2P network to interact with the decentralizedP2P network.

As will be described in further detail below, a decentralized P2P systemimplementing a blockchain data structure may provide solutions totechnological problems existing in current centralized system constructswith traditional data storage arrangements. For example, conventionaldata storage arrangements that use a central data authority have asingle point of failure (namely, the central storage location) which, ifcompromised by a malicious attacker, can lead to data tampering,unauthorized data disclosure, and exploitation and/or loss of operativecontrol of the processes performed by the centralized system. Theimplementation of a blockchain data structure in a decentralized P2Psystem acts as a safeguard against unreliable and/or malicious nodesacting in the decentralized P2P network to undermine the work efforts ofthe other nodes, e.g., by providing byzantine fault tolerance within thenetwork.

Computing Architectures

FIG. 1 depicts an illustrative example of centralized computer system100 in accordance with one or more illustrative aspects describedherein. Centralized computer system 100 may comprise one or morecomputing devices including at least server infrastructure 110 and usercomputing devices 120. Each of user computing devices 120 may beconfigured to communicate with server infrastructure 110 through network130. In some arrangements, centralized computer system 100 may includeadditional computing devices and networks that are not depicted in FIG.1, which also may be configured to interact with server infrastructure110 and, in some instances, user computing devices 120.

Server infrastructure 110 may be associated with a distinct entity suchas a company, school, government, and the like, and may comprise one ormore personal computer(s), server computer(s), hand-held or laptopdevice(s), multiprocessor system(s), microprocessor-based system(s), settop box(es), programmable consumer electronic device(s), networkpersonal computer(s) (PC), minicomputer(s), mainframe computer(s),distributed computing environment(s), and the like. Serverinfrastructure 110 may include computing hardware and software that mayhost various data and applications for performing tasks of thecentralized entity and interacting with user computing devices 120, aswell as other computing devices. For example, each of the computingdevices comprising server infrastructure 110 may include at least one ormore processors 112 and one or more databases 114, which may be storedin memory of the one or more computing devices of server infrastructure110. Through execution of computer-readable instructions stored inmemory, the computing devices of server infrastructure 110 may beconfigured to perform functions of the centralized entity and store thedata generated during the performance of such functions in databases114.

In some arrangements, server infrastructure 110 may include and/or bepart of enterprise information technology infrastructure and may host aplurality of enterprise applications, enterprise databases, and/or otherenterprise resources. Such applications may be executed on one or morecomputing devices included in server infrastructure 110 usingdistributed computing technology and/or the like. In some instances,server infrastructure 110 may include a relatively large number ofservers that may support operations of a particular enterprise ororganization, such as a financial institution. Server infrastructure110, in this embodiment, may generate a single centralized ledger fordata received from the various user computing devices 120, which may bestored in databases 114.

Each of the user computing devices 120 may be configured to interactwith server infrastructure 110 through network 130. In some instances,one or more of the user computing devices 120 may be configured toreceive and transmit information corresponding to system requeststhrough particular channels and/or representations of webpages and/orapplications associated with server infrastructure 110. The systemrequests provided by user computing devices 120 may initiate theperformance of particular computational functions such as data and/orfile transfers at server infrastructure 110. In such instances, the oneor more of the user computing devices may be internal computing devicesassociated with the particular entity corresponding to serverinfrastructure 110 and/or may be external computing devices which arenot associated with the particular entity.

As stated above, centralized computer system 100 also may include one ormore networks, which may interconnect one or more of serverinfrastructure 110 and one or more user computing devices 120. Forexample, centralized computer system 100 may include network 130.Network 130 may include one or more sub-networks (e.g., local areanetworks (LANs), wide area networks (WANs), or the like). Furthermore,centralized computer system 100 may include a local network configuredto each of the computing devices comprising server infrastructure 110.The local network connecting auto identification and mapping computingplatform 120, system infrastructure 130, and/or post-performance reviewcomputing device 140 may interface with network 150 and enablecommunication with user computing devices 110A-110N.

Furthermore, in some embodiments, centralized computer system 100 mayinclude a plurality of computer systems arranged in an operativenetworked communication with one another through a network, which mayinterface with server infrastructure 110, user computing devices 120,and network 130. The network may be a system specific distributivenetwork receiving and distributing specific network feeds andidentifying specific network associated triggers. The network may alsobe a global area network (GAN), such as the Internet, a wide areanetwork (WAN), a local area network (LAN), or any other type of networkor combination of networks. The network may provide for wireline,wireless, or a combination wireline and wireless communication betweendevices on the network.

In the centralized computer system 100 described in regard to FIG. 1,server infrastructure 110 may serve as a central authority which managesat least a portion of the computing data and actions performed inrelation to the particular entity associated with server infrastructure110. As such, server infrastructure 110 of centralized computer system100 provides a single point of failure that, if compromised by amalicious attacker, can lead to data tampering, unauthorized datadisclosure, and exploitation and/or loss of operative control of theprocesses performed by the server infrastructure 110 in relation to theparticular entity associated with server infrastructure 110. In such acentralized construct in which a single point of failure (e.g., serverinfrastructure 110) is created, significant technological problems ariseregarding maintenance of operation and data control, as well aspreservation of data integrity. As will be described in further detailbelow in regard to FIG. 2, such technological problems existing incentralized computing arrangements may be solved by a decentralized P2Psystem implementing a blockchain data structure, even wholly within theserver infrastructure 110.

FIG. 2 depicts an illustrative example of decentralized P2P computersystem 200 that may be used in accordance with one or more illustrativeaspects described herein. Decentralized P2P computer system 200 mayinclude a plurality of full node computing devices 210A, 210B, 210C,210D, 210E, and 210F and lightweight node computing devices 250A and250B, which may be respectively similar to full node computing device210 described in regard to FIG. 3A and lightweight node computing device250 described in regard to FIG. 3B. While a particular number of fullnode computing devices and lightweight node computing devices aredepicted in FIG. 2, it should be understood that a number of full nodecomputing devices and/or lightweight node computing devices greater orless than that of the depicted full node computing devices andlightweight node computing devices may be included in decentralized P2Pcomputer system 200. Accordingly, any additional full node computingdevices and/or lightweight node computing devices may respectivelyperform in the manner described below in regard to full node computingdevices 210A-210F and lightweight node computing devices 250A and 250Bin decentralized P2P computer system 200.

Each of full node computing devices 210A-210F may operate in concert tocreate and maintain decentralized P2P network 270 of decentralized P2Pcomputer system 200. In creating decentralized P2P network 270 ofdecentralized P2P computer system 200, processors, ASIC devices, and/orgraphics processing units (e.g., GPUs) of each full node computingdevice 210A-210F may execute network protocols which may cause each fullnode computing device 210A-210F to form a communicative arrangement withthe other full node computing devices 210A-210F in decentralized P2Pcomputer system 200 and create decentralized P2P network 270.Furthermore, the execution of network protocols by the processors, ASICdevices, and/or graphics processing units (e.g., GPUs) of full nodecomputing devices 210A-210F may cause full node computing devices210A-210F to execute network functions related to blockchain 226 andthereby maintain decentralized P2P network 270.

Lightweight node computing devices 250A and 250B may request executionof network functions related to blockchain 226 in decentralized P2Pnetwork 270. In order to request execution of network functions, such asstoring transaction information and/or smart contract operations,processors of lightweight node computing devices 250A and 250B mayexecute network commands to broadcast the network functions todecentralized P2P network 270 comprising full node computing devices210A-210F.

For example, lightweight node computing device 250A may requestexecution of a transaction related to blockchain 226 in decentralizedP2P network 270, which may entail a data transfer from a private/publickey associated with lightweight node computing device 250A to aprivate/public key associated with lightweight node 250B. In doing so,processors of lightweight node computing device 250A may execute networkcommands to broadcast balance sheet transaction network function request280 to decentralized P2P network 270. Balance sheet transaction networkfunction request 280 may include details about the data transfer such asdata type and amount, as well as a data transfer amount to full nodecomputing devices 210A-210F of decentralized P2P network 270 forexecuting balance sheet transaction network function request 280.Balance sheet transaction network function request 280 may furtherinclude the public key associated with lightweight node computing device250B. Processors of lightweight node computing device 250A may executedigital signature algorithms to digitally sign balance sheet transactionnetwork function request 280 with the private key associated withlightweight node computing device 250A.

At decentralized P2P network 270, balance sheet transaction networkfunction request 280 may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute balance sheettransaction network function request 280 and maintain inter-nodalagreement as to the state of blockchain 226, processors, ASIC devices,and/or GPUs of full node computing devices 210A-210F may execute networkprotocols to receive broadcast of the network function through adecentralized P2P network 270 and from lightweight node computing device250A. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute hash functions to generate a digest ofbalance sheet transaction network function request 280. The resultantdigest of balance sheet transaction network function request 280, inturn, may be hashed with the block hash of the most immediatelypreceding block of blockchain 226. Processors, ASIC devices, and/or GPUsof full node computing devices 210A-210F may execute consensusalgorithms to identify a numerical value (e.g., nonce) corresponding tothe particular executed consensus algorithm and related to the digestthat combines the digest of the balance sheet transaction networkfunction request 280 and the block hash of the most immediatelypreceding block of blockchain 226.

For example, in embodiments in which the consensus algorithm is proof ofwork (e.g., PoW), processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210F may perform a plurality of hashingoperations to identify a nonce that, when hashed with the digest thatcombines the digest of the balance sheet transaction network functionrequest 280 and the block hash of the most immediately preceding blockof blockchain 226, produces a hash of a predetermined alphanumericalformat. Such a predetermined alphanumerical format may include apredetermined number of consecutive alphanumerical characters at apredetermined position within the resultant digest that combines thenonce, digest of the balance sheet transaction network function request280, and block hash of the most immediately preceding block ofblockchain 226.

In embodiments in which the consensus algorithm is proof of stake (e.g.,PoS), a private key associated with one of full node computing devices210A-210F may be pseudo-randomly selected, based on balance sheetholdings associated with the public keys of full node computing devices210A-210F, to serve as the nonce. For example, through execution of thePoS consensus algorithm, full node computing devices 210A-210F areentered into a lottery in which the odds of winning are proportional toa balance sheet amount associated the public key of each of full nodecomputing devices 210A-210F, wherein a larger balance sheet amountcorresponds to a higher probability to win the lottery. The PoSconsensus algorithm may cause a full node computing device from fullnode computing devices 210A-210F to be selected, and the public key ofthe selected full node computing device to be used as the nonce.

In embodiments in which the consensus algorithm is delegated proof ofstake (e.g., DPoS), a group of delegates are chosen from full nodecomputing devices 210A-210F by each of computing devices 210A-210F,wherein full node computing devices 210A-210F are allowed to vote ondelegates based on balance sheet holdings associated with the respectivepublic keys. Full node computing devices 210A-210F, however, may notvote for themselves to be delegates. Once the group of delegates arechosen, the group of delegates from full node computing devices210A-210F select a public key associated with one of full node computingdevices 210A-210F to serve as the nonce. Again, each of the delegatesare prohibited from selecting themselves and their respective public keyfrom serving as the nonce.

In embodiments in which the consensus algorithm is practical byzantinefault tolerance algorithm (e.g., PBFT), each of full node computingdevices 210A-210F are associated with a particular status and/or ongoingspecific information associated with the respective public key of thefull node computing devices. Each of full node computing devices210A-210F receive a message through decentralized P2P network 270 basedon network protocols. Based on the received message and particularstatus and/or ongoing specific information, each of full node computingdevices 210A-210F perform computational tasks and transmit a response tothe tasks to each of the other full node computing devices 210A-210F. Apublic key associated with a particular full node computing device fromfull node computing devices 210A-210F is selected by each of full nodecomputing devices 210A-210F based on the response of the particular fullnode computing device best fulfilling criteria determined based on thenetwork protocols.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines the digest of balance sheet transactionnetwork function request 280, the block hash of the most immediatelypreceding block, and the identified nonce. Processors, ASIC devices,and/or GPUs of the full node computing device from full node computingdevices 210A-210F may execute network protocols to add the new block toblockchain 226 and broadcast the new block to the other full nodecomputing devices in the decentralized P2P network 270. In somearrangements, the new block may also be time-stamped at a timecorresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may beallowed, per the network protocols, to increase a balance sheet holdingsamount associated with itself by a predetermined amount. In somearrangements, each of full node computing devices 210A-210F may receivean equal portion of the data transfer amount specified by lightweightnode computing device 260A for executing balance sheet transactionnetwork function request 280. After the new block has been added toblockchain 226, balance sheet transaction network function request 280may be considered to be executed and the data transfer from theprivate/public key associated with lightweight node computing device250A to the private/public key associated with lightweight node 250B maybe registered.

As stated above, in some arrangements, a plurality of network functionrequests may be broadcasted across decentralized network P2P network270. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute network protocols to receive broadcast ofeach of the network functions, including balance sheet transactionnetwork function request 280, through decentralized P2P network 270 andfrom the requesting entities, including lightweight node computingdevice 250A. Processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210F may execute hash functions to generate ahash tree (e.g., Merkle tree) of the requested network functions, whichculminates in a single digest (e.g., root digest, root hash, and thelike) that comprises the digests of each of the requested networkfunctions, including balance sheet transaction network function request280. The root digest of the requested network function, in turn, may behashed with the block hash of the most immediately preceding block ofblockchain 226. Processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210B may execute consensus algorithms in themanner described above to identify a nonce corresponding to theparticular executed consensus algorithm and related to the digest thatcombines the root digest of the requested network functions and theblock hash of the most immediately preceding block of blockchain 226.The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines the root digest of the network functionrequests, the block hash of the most immediately preceding block, andthe identified nonce. Processors, ASIC devices, and/or GPUs of the fullnode computing device from full node computing devices 210A-210F mayexecute network protocols to add the new block to blockchain 226 andbroadcast the new block to the other full node computing devices in thedecentralized P2P network 270. In some arrangements, the new block mayalso be time-stamped at a time corresponding to the addition toblockchain 226. Furthermore, as a reward for adding the new block toblockchain 226, the full node computing device from full node computingdevices 210A-210F may be allowed, per the network protocols, to increasea balance sheet holdings amount associated with itself by apredetermined amount. In some arrangements, each of full node computingdevices 210A-210F may receive an equal portion of the data transferamount specified by each of the network function requests. After the newblock has been added to blockchain 226, each of the network functionsrequests, including balance sheet transaction network function request280, may be considered to be executed and the data transfer from theprivate/public key associated with lightweight node computing device250A to the private/public key associated with lightweight node 250B maybe registered.

While the description provided above is made in relation to a balancesheet transaction involving lightweight node computing device 250A andlightweight node computing device 250B, it is to be understood thatbalance sheet transactions are not limited to lightweight node computingdevice 250A and lightweight node computing device 250B, but rather maybe made across any of the full node computing devices and/or lightweightnode computing devices in decentralized P2P system 200.

For another example, lightweight node computing device 250B may requesta smart contract operation related to decentralized P2P network 270,which may facilitate a dual data transfer between a wallet associatedwith lightweight node computing device 250B and a wallet associated withanother node in decentralized P2P network 270, such as lightweight nodecomputing device 250A, based on fulfillment of programmatic conditionsestablished by a smart contract. Processors of lightweight nodecomputing device 250B may execute network commands to broadcast smartcontract operation network function request 290 to decentralized P2Pnetwork 270. Smart contract operation network function request 290 mayinclude details about the data transfer such as data type and amount, aswell as a data transfer amount to full node computing devices 210A-210Fof decentralized P2P network 270 for executing the smart contractcorresponding to smart contract operation network function request 290.Smart contract operation network function request 290 may furtherinclude the public key associated with the smart contract. Processors oflightweight node computing device 250B may execute digital signaturealgorithms to digitally sign smart contract operation network functionrequest 290 with the private key associated with the wallet oflightweight node computing device 250B.

At decentralized P2P network 270, smart contract operation networkfunction request 290 may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute smart contractoperation network function request 290 and maintain inter-nodalagreement as to the state of blockchain 226, processors, ASIC devices,and/or GPUs of full node computing devices 210A-210F may execute networkprotocols to receive broadcast of the network function through adecentralized P2P network 270 and from lightweight node computing device250B. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute hash functions to generate a digest ofsmart contract operation network function request 290. The resultantdigest of smart contract operation network function request 290, inturn, may be hashed with the block hash of the most immediatelypreceding block of blockchain 226. Processors, ASIC devices, and/or GPUsof full node computing devices 210A-210F may execute consensusalgorithms to identify a nonce corresponding to the particular executedconsensus algorithm and related to the digest that combines the digestof smart contract operation network function request 290 and the blockhash of the most immediately preceding block of blockchain 226.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines smart contract operation networkfunction request 290, the block hash of the most immediately precedingblock, and the identified nonce. Processors, ASIC devices, and/or GPUsof the full node computing device from full node computing devices210A-210F may execute network protocols to add the new block toblockchain 226 and broadcast the new block to the other full nodecomputing devices in the decentralized P2P network 270. In somearrangements, the new block may also be time-stamped at a timecorresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may, per thenetwork protocols, increase a balance sheet holdings amount associatedwith itself by a predetermined amount. In some arrangements, each offull node computing devices 210A-210F may receive an equal portion ofthe data transfer amount specified by lightweight node computing device250B for executing smart contract operation network function request290. After the new block has been added to blockchain 226, smartcontract operation request 290 may be considered to be executed and thedata transfer from the wallet associated with lightweight node computingdevice 250B to the public key associated with the smart contract may beregistered.

The smart contract may be configured to hold the data transfer from thewallet associated with lightweight node computing device 250B untilfulfillment of certain predetermined criteria hardcoded into the smartcontract are achieved. The smart contract may be configured such that itserves as an intermediate arbiter between entities within thedecentralized P2P network 270 and may specify details of a dual datatransfer between entities.

For example, the smart contract corresponding to smart contractoperation request 290 may be one or more algorithms and/or programsstored on a block of blockchain 226. The smart contract may beidentified by one or more wallets and/or public keys withindecentralized P2P network 270. Lightweight node computing device 250Bmay transmit smart contract operation network function request 290 todecentralized P2P network 270, which may cause execution of thecorresponding smart contract that facilitates a dual data transferbetween a wallet associated with lightweight node computing device 250Band a wallet associated with another node in decentralized P2P network270, such as lightweight node computing device 250A, based onfulfillment of programmatic conditions established by the smartcontract. In the processes of adding the block comprising smart contractoperation request 290 to blockchain 226, each of full node computingdevices 210A-210F may identify the block within blockchain 226comprising the smart contract, associate the data transfer entailed bysmart contract operation request 290 with the smart contract, andexecute the one or more algorithms and/or programs of the smartcontract. In this instance, given that the smart contract facilitates adual data transfer and that data transfer has yet to be received fromanother node (e.g., lightweight node computing device 250A), each offull node computing devices 210A-210F may execute the smart contractwithout fulfillment of the programmatic conditions established by thesmart contract. Accordingly, the funds transferred by lightweight nodecomputing device 250B may remain in the smart contract until the datatransfer from the other node is also associated with the smart contract.

Moving forward, lightweight node computing device 250A may also requesta smart contract operation related to decentralized P2P network 270,which may conclude the dual data transfer between the wallet associatedwith lightweight node computing device 250A and the wallet associatedwith lightweight node computing device 250B. Processors of lightweightnode computing device 250A may execute network commands to broadcast thesmart contract operation network function request to decentralized P2Pnetwork 270. The smart contract operation network function request mayinclude details about the data transfer such as data type and amount, aswell as a data transfer amount to full node computing devices 210A-210Fof decentralized P2P network 270 for executing the smart contractcorresponding to the smart contract operation network function request.The smart contract operation network function request may furtherinclude the public key associated with the smart contract. Processors oflightweight node computing device 250A may execute digital signaturealgorithms to digitally sign the smart contract operation networkfunction request with the private key associated with the wallet oflightweight node computing device 250A.

At decentralized P2P network 270, the smart contract operation networkfunction request may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute the smart contractoperation network function request and maintain inter-nodal agreement asto the state of blockchain 226, processors, ASIC devices, and/or GPUs offull node computing devices 210A-210F may execute network protocols toreceive broadcast of the network function through a decentralized P2Pnetwork 270 and from lightweight node computing device 250A. Processors,ASIC devices, and/or GPUs of full node computing devices 210A-210F mayexecute hash functions to generate a digest of the smart contractoperation network function request. The resultant digest of the smartcontract operation network function request, in turn, may be hashed withthe block hash of the most immediately preceding block of blockchain226. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute consensus algorithms to identify a noncecorresponding to the particular executed consensus algorithm and relatedto the digest that combines the digest of the smart contract operationnetwork function request and the block hash of the most immediatelypreceding block of blockchain 226.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines the smart contract operation networkfunction request, the block hash of the most immediately precedingblock, and the identified nonce. Processors, ASIC devices, and/or GPUsof the full node computing device from full node computing devices210A-210F may execute network protocols to add the new block toblockchain 226 and broadcast the new block to the other full nodecomputing devices in the decentralized P2P network 270. In somearrangements, the new block may also be time-stamped at a timecorresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may beallowed, per the network protocols, to increase a balance sheet holdingsamount associated with itself by a predetermined amount. In somearrangements, each of full node computing devices 210A-210F may receivean equal portion of the data transfer amount specified by lightweightnode computing device 250A for executing the smart contract operationnetwork function request. After the new block has been added toblockchain 226, the smart contract operation transaction networkfunction request 290 may be considered to be executed and the datatransfer from the wallet associated with lightweight node computingdevice 250A to the public key associated with the smart contract may beregistered.

When the smart contract receives the data value from each of lightweightnode computing device 250A and lightweight node computing device 250B,the execution of the smart contract by each of full node computingdevices 210A-210F may cause transfer of the data value from lightweightnode computing device 250A to lightweight node computing device 250B andthe data value from lightweight node computing device 250B tolightweight node computing device 250A.

For example, lightweight node computing device 250A may transmit thesmart contract operation network function request to decentralized P2Pnetwork 270, which may cause execution of the corresponding smartcontract that facilitates the dual data transfer. In the process ofadding the block comprising the smart contract operation requestprovided by lightweight node computing device 250A to blockchain 226,each of full node computing devices 210A-210F may identify the blockwithin blockchain 226 comprising the smart contract, associate the datatransfer entailed by smart contract operation request of lightweightnode computing device 250A with the smart contract, and execute the oneor more algorithms and/or programs of the smart contract. In thisinstance, given that the smart contract facilitates a dual data transferand that data transfers have been received from lightweight nodecomputing device 250A and lightweight node computing device 250B, eachof full node computing devices 210A-210F may execute the smart contractas fulfillment of the programmatic conditions established by the smartcontract has occurred. Accordingly, the funds allocated to the smartcontract by each of lightweight node computing device 250A andlightweight node computing device 250B may be respectively distributedto the intended counterparty.

While the description provided above was made in relation to lightweightnode computing device 250A and lightweight node computing device 250B,it should be understood that any of the full node computing devices andlightweight node computing devices in decentralized system 200 mayparticipate in the smart contract. Furthermore, it should be understoodthat the smart contract may be able to fulfill dual data transfers inthe manner described above across a plurality of entities entering intothe smart contract. For example, a first plurality of entities may enterinto the smart contract, which may hold the data values for each of thefirst plurality of entities until a second plurality of entities enterinto the smart contract. When each of the first plurality of entitiesand the second plurality of entities have entered, the smart contractmay perform the data transfer. Other smart contracts may be includedwhich include algorithms, programs, and/or computer-executableinstructions which cause the performance of one or more functionsrelated to at least cryptocurrency, digital content storage anddelivery, entity authentication and authorization, digital identity,marketplace creation and operation, internet of things (e.g., IoT),prediction platforms, election voting, medical records, currencyexchange and remittance, P2P transfers, ride sharing, gaming, tradingplatforms, and real estate, precious metal, and work of art registrationand transference.

In comparison to the centralized computing system 100 described inregard to FIG. 1, decentralized P2P computer system 200 may providetechnological advantages. For example, by distributing storage ofblockchain 226 across multiple full node computing devices 210A-210F,decentralized P2P computer system 200 may not provide a single point offailure for malicious attack. In the event that any of the full nodecomputing devices 210A-210F are compromised by a malicious attacker,decentralized P2P computer system 200 may continue to operate unabatedas data storage of blockchain 226 and network processes are notcontrolled by a singular entity such as server infrastructure 110 ofcentralized computing system 100.

Furthermore, by utilizing blockchain data structure 226, decentralizedP2P system 200 may provide technological improvements to conventionaldecentralized P2P systems in regard to byzantine fault tolerancestemming from an unreliable and/or malicious full node acting indecentralized P2P network 270 to undermine the work efforts of the othernodes. For example, in coordinating action between full node computingdevices 210A-210F in relation to a similar computational task (e.g.,consensus algorithm), a malicious node would need to have computationalpower greater than the combined computational power of each of the otherfull node computing devices in decentralized P2P network 270 to identifythe nonce and thereby be able to modify blockchain 226. As such, thelikelihood that a malicious node could subvert decentralized P2P network270 and enter falsified data into blockchain 270 is inverselyproportional to the total computational power of decentralized P2Psystem 200. Therefore, the greater the total computational power ofdecentralized P2P system 200, the less likely that a malicious nodecould subvert decentralized P2P network 270 and undermine blockchain226.

FIG. 3A depicts an illustrative example of a full node computing device210 that may be used in accordance with one or more illustrative aspectsdescribed herein. Full node computing device 210 may be any of apersonal computer, server computer, hand-held or laptop device,multiprocessor system, microprocessor-based system, set top box,programmable consumer electronic device, network personal computer,minicomputer, mainframe computer, distributed computing environment,virtual computing device, and the like and may operate in adecentralized P2P network. In some embodiments, full node computingdevice 210 may be configured to operate in a decentralized P2P networkand may request execution of network functions and/or to executerequested network functions and maintain inter-nodal agreement as to thestate of a blockchain of the decentralized P2P network.

Full node computing device 210 may include one or more processors 211,which control overall operation, at least in part, of full nodecomputing device 210. Full node computing device 210 may further includerandom access memory (RAM) 213, read only memory (ROM) 214, networkinterface 212, input/output interfaces 215 (e.g., keyboard, mouse,display, printer, and the like), and memory 220. Input/output (I/O) 215may include a variety of interface units and drives for reading,writing, displaying, and/or printing data or files. In somearrangements, full node computing device 210 may further comprisespecialized hardware components such as application-specific integratedcircuit (e.g., ASIC) devices 216 and/or graphics processing units (e.g.,GPUs) 217. Such specialized hardware components may be used by full nodecomputing device 210 in performing one or more of the processes involvedin the execution of requested network functions and maintenance ofinter-nodal agreement as to the state of a blockchain. Full nodecomputing device 210 may further store in memory 220 operating systemsoftware for controlling overall operation of the full node computingdevice 210, control logic for instructing full node computing device 210to perform aspects described herein, and other application softwareproviding secondary, support, and/or other functionality which may ormight not be used in conjunction with aspects described herein.

Memory 220 may also store data and/or computer executable instructionsused in performance of one or more aspects described herein. Forexample, memory 220 may store digital signature information 221 and oneor more hash functions 222, consensus algorithms 223, network protocols224, and network commands 225. In some arrangements, digital signatureinformation 221, hash functions 222, and/or network commands 225 maycomprise a wallet of full node computing device 210. Memory 220 mayfurther store blockchain 226. Each of digital signature information 221,hash functions 222, consensus algorithms 223, network protocols 224, andnetwork commands 225 may be used and/or executed by one or moreprocessors 211, ASIC devices 216, and/or GPUs 217 of full node computingdevice 210 to create and maintain a decentralized P2P network, requestexecution of network functions, and/or execute requested networkfunctions and maintain inter-nodal agreement as to the state ofblockchain 226.

For example, in order to create and maintain a decentralized P2Pnetwork, processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 may execute network protocols 225. Execution ofnetwork protocols 225 may cause full node computing device 210 to form acommunicative arrangement with other full node computing devices andthereby create a decentralized P2P network. Furthermore, the executionof network protocols 225 may cause full node computing device 210 tomaintain the decentralized P2P network through the performance ofcomputational tasks related to the execution of network requests relatedto a blockchain such as blockchain 226. As will be described in detailbelow, the execution of such computational tasks (e.g., hash functions222, consensus algorithms 223, and the like) may cause full nodecomputing device 210 to maintain inter-nodal agreement as to the stateof a blockchain with other full node computing devices comprising thedecentralized P2P network.

In order to request execution of network functions, such as balancesheet transactions and/or smart contract operations, processors 211,ASIC devices 216, and/or GPUs 217 of full node computing device 210 mayexecute network commands 225 to broadcast the network function to adecentralized P2P network comprising a plurality of full nodes and/orlightweight nodes. The request may be digitally signed by full nodecomputing device 210 with usage of the private/public key informationand through execution of the digital signature algorithms of digitalsignature information 221.

In order to execute requested network functions and maintain inter-nodalagreement as to the state of a blockchain, processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may executenetwork protocols 224 to receive a broadcast of a requested networkfunction through a decentralized P2P network and from a requestingentity such as a full node or lightweight node. Processors 211, ASICdevices 216, and/or GPUs 217 of full node computing device 210 mayexecute hash functions 222 to generate a digest of the requested networkfunction. The resultant digest of the requested network function, inturn, may be hashed with the block hash of the most immediatelypreceding block of the blockchain. As will be described in furtherdetail below, processors 211, ASIC devices 216, and/or GPUs 217 of fullnode computing device 210 may execute consensus algorithms 223 toidentify a numerical value (e.g., nonce) corresponding to the particularexecuted consensus algorithm and related to the digest that combines thedigest of the requested network function and the block hash of the mostimmediately preceding block of the blockchain. The identification of thenumerical value enables processors 211, ASIC devices 216, and/or GPUs217 of full node computing device 210 to create a new block with a blockheader (e.g., block hash), which is a digest that combines the digest ofthe requested network function, the block hash of the most immediatelypreceding block, and the identified nonce. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may add the newblock to the blockchain based on network protocols 224 and broadcast thenew block to the other nodes in the decentralized P2P network.

As stated above, in some arrangements, a plurality of network functionrequests may be broadcasted across the decentralized network P2Pnetwork. Processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 may execute network protocols 224 to receivebroadcast of each of the network functions through the decentralized P2Pnetwork and from the requesting entities. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may execute hashfunctions 222 to generate a hash tree (e.g., Merkle tree) of therequested network functions, which culminates in a single digest (e.g.,root digest, root hash, and the like) that comprises the digests of eachof the requested network functions. The root digest of the requestednetwork function, in turn, may be hashed with the block hash of the mostimmediately preceding block of the blockchain. Processors 211, ASICdevices 216, and/or GPUs 217 of full node computing device 210 mayexecute consensus algorithms 223 to identify a numerical value (e.g.,nonce) corresponding to the particular executed consensus algorithm andrelated to the digest that combines the root digest of the requestednetwork functions and the block hash of the most immediately precedingblock of the blockchain. The identification of the numerical valueenables processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 to create a new block with a block header (e.g.,block hash), which is a digest that combines the root digest of therequested network functions, the block hash of the most immediatelypreceding block, and the identified nonce. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may add the newblock to the blockchain based on network protocols 224 and broadcast thenew block to the other nodes in the decentralized P2P network.

Furthermore, memory 220 of full node computing device 210 may storeblockchain 226. Blockchain 226 may include a blocks 227A, 227B, 227C, .. . 227 n, wherein block 227A represents the first block (e.g., genesisblock) of blockchain 226 and block 227 n represents the most immediateblock of blockchain 226. As such, the blockchain 226, which may be areplica or copy of the blockchain of the decentralized P2P network inwhich full node computing device 210 operates, may be a full or completecopy of the blockchain of the decentralized P2P network. Each of theblocks within blockchain 226 may include information corresponding tothe one or more network functions executed by the decentralized P2Pnetwork. As such, blockchain 226 as stored in memory 220 of full nodecomputing device 210 may comprise the totality of network functionsexecuted by the decentralized network.

FIG. 3B depicts an illustrative example of a lightweight node computingdevice 250 that may be used in accordance with one or more illustrativeaspects described herein. Lightweight node computing device 250 may beany of a personal computer, server computer, hand-held or laptop device,multiprocessor system, microprocessor-based system, set top box,programmable consumer electronic device, network personal computer,minicomputer, mainframe computer, distributed computing environment,virtual computing device, and the like and may operate in adecentralized P2P network. In some embodiments, lightweight nodecomputing device 250 may operate in a decentralized P2P network and maybe configured to request execution of network functions through thedecentralized P2P network. As such, lightweight node computing device250 may be different than full node computing device 210 in that it isnot configured to execute network functions and/or operate to maintain ablockchain of a decentralized P2P network. In other aspects, lightweightnode computing device 250 may have substantially the same physicalconfiguration as full node computing device 210, but configured withdifferent programs, software, and the like

Lightweight node computing device 250 may include one or more processors251, which control overall operation of lightweight node computingdevice 250. Lightweight node computing device 250 may further includerandom access memory (RAM) 253, read only memory (ROM) 254, networkinterface 252, input/output interfaces 255 (e.g., keyboard, mouse,display, printer, and the like), and memory 260. Input/output (I/O) 255may include a variety of interface units and drives for reading,writing, displaying, and/or printing data or files. Lightweight nodecomputing device 250 may store in memory 260 operating system softwarefor controlling overall operation of the lightweight node computingdevice 250, control logic for instructing lightweight node computingdevice 250 to perform aspects described herein, and other applicationsoftware providing secondary, support, and/or other functionality whichmay or might not be used in conjunction with aspects described herein.

In comparison to full node computing device 210, lightweight nodecomputing device 250 might not include, in some instances, specializedhardware such as ASIC devices 216 and/or GPUs 217. Such is the casebecause lightweight node computing device 250 might not be configured toexecute network functions and/or operate to maintain a blockchain of adecentralized P2P network as is full node computing device 210. However,in certain arrangements, lightweight node computing device 250 mayinclude such specialized hardware.

Memory 260 of lightweight node computing device 250 may also store dataand/or computer executable instructions used in performance of one ormore aspects described herein. For example, memory 260 may store digitalsignature information 261 and one or more hash functions 222 and networkcommands 225. In some arrangements, digital signature information 261,hash functions 222, and/or network commands 225 may comprise a wallet oflightweight node computing device 250. Each of hash functions 222 andnetwork commands 225 stored in memory 260 of lightweight node computingdevice 250 may be respectively similar and/or identical to hashfunctions 222 network commands 225 stored in memory 220 of full nodecomputing device 210.

In regard to the digital signature information, each of digitalsignature information 261 stored in memory 260 of lightweight nodecomputing device 250 and digital signature information 221 stored inmemory 220 of full node computing device 210 may comprise similar and/oridentical digital signature algorithms. However, the private/public keyinformation of digital signature information 261 stored in memory 260 oflightweight node computing device 250 may be different than that of theprivate/public key information of digital signature information 221stored in memory 220 of full node computing device 210. Furthermore, theprivate/public key information of each node, whether full orlightweight, in a decentralized P2P computing network may be unique tothat particular node. For example, a first node in a decentralized P2Pcomputing network may have first private/public key information, asecond node may have second private/public key information, a third nodemay have third private/public key information, and so on, wherein eachof the private/public key information is unique to the particular node.As such, the private/public key information may serve as a uniqueidentifier for the nodes in a decentralized P2P computing network.

Each of digital signature information 261, hash functions 222, andnetwork commands 225 may be used and/or executed by one or moreprocessors 251 of lightweight node computing device 250 to requestexecution of network functions in a decentralized P2P network. Forexample, in order to request execution of network functions, such asbalance sheet transactions and/or smart contract operations, processors251 of lightweight node computing device 250 may execute networkcommands 225 to broadcast the network function to a decentralized P2Pnetwork comprising a plurality of full nodes and/or lightweight nodes.The request may be digitally signed by lightweight node computing device250 with usage of the private/public key information and throughexecution of the digital signature algorithms of digital signatureinformation 261.

Furthermore, memory 260 of lightweight node computing device 250 maystore blockchain 226. Blockchain 226 stored in memory 260 of lightweightnode computing device 250 may include at least block 227 n, whereinblock 227 n represents the most immediate block of blockchain 226. Assuch, the blockchain 226, which may be a replica or copy of theblockchain of the decentralized P2P network in which lightweight nodecomputing device 250 operates, may be a partial or incomplete copy ofthe blockchain of the decentralized P2P network. In some instances,however, blockchain 226 may include a blocks 227A, 227B, 227C, . . . 227n, wherein block 227A represents the first block (e.g., genesis block)of blockchain 226 and block 227 n represents the most immediate block ofblockchain 226. As such, the blockchain 226 may be a full or completecopy of the blockchain of the decentralized P2P network. Each of theblocks within blockchain 226 may include information corresponding tothe one or more network functions executed by the decentralized P2Pnetwork.

Block Chains Enriched with Event and Trust Information

Smart contracts, as described above, provide automatic execution oftransactions according to programmatic conditions. Although smartcontracts may partially mitigate the necessity of determining whether acounterparty can be trusted, smart contracts may, in some cases, beincomplete. Contracts cannot account for every contingency, andunforeseen disagreements may arise that may make further negotiation(beyond the provisions of a smart contract) necessary to resolve adispute. Due to the possibility of such situations, entities thatconduct transactions either on or off a block chain may be concernedwith ensuring they can trust a transaction counterparty, even when smartcontracts are used.

Blockchains enriched with event and/or trust information may provideadditional information about a potential transaction counterparty thatmay help increase trust in the counterparty. Such enriched blockchainsmay include a history of information about a user or a corporate entityand trust information derived therefrom. The historical information mayinclude previous transactions involving the user or corporate entity,background information about the user or corporate entity, as well assupply chain information for a corporate entity. Multiple blockchainsmay store such information in order to increase the scalability of thesystem. For example, a main blockchain may include trust information forusers and/or corporate entities, while several sidechains may includehistorical information (which may include a very large volume of eventinformation) for the users and/or corporate entities.

FIG. 4 depicts an illustrative system and operating environment forimplementing features of the present disclosure, including generatingand maintaining a blockchain containing trust information for users. Anautomated event processing computing platform 410 may connect to ablockchain network, such as blockchain network 200 illustrated at FIG.2. The automated event processing computing platform 410 may implement anode of the blockchain network, such as a lightweight node 250 and/or(as illustrated) a full node 210 such that the automated eventprocessing computing platform 410 may participate in the one or moreblockchains of the blockchain network 200. The automated eventprocessing computing platform 410 may implement the node as a physicaldevice that makes up part of the automated event processing computingplatform 410 and/or may implement the node as a virtualized deviceand/or software module running inside hardware of the automated eventprocessing computing platform 410. In some examples, the automated eventprocessing computing platform 410 may implement multiple (e.g.,virtualized) nodes that interact with multiple blockchains (e.g., oneblockchain per node) on the same blockchain network 200 and/or differentblockchain networks.

The automated event processing computing platform 410 may connect to theblockchain network 200 through intermediate networks, including privatenetworks, the Internet, or any other networks. The automated eventprocessing computing platform 410 may further connect to one or morethird party computing devices 440, which may interact with the automatedevent processing computing platform 410 and or other devices connectedto the blockchain network 200 to perform various functions. The thirdparty computing devices 440 may implement a full node 210 and/or (asillustrated) a lightweight node 250 in order to interact with theblockchain network 200. The third party computing device 440 mayimplement the node as a physical device that makes up part of the thirdparty computing device 440 and/or may implement the node as avirtualized device and/or software module running inside hardware of thethird party computing device 440. In some examples, the third partycomputing device 440 may implement multiple (e.g., virtualized) nodesthat interact with multiple blockchains (e.g., one blockchain per node)on the same blockchain network 200 and/or different blockchain networks.For example, various ones of the third party computing devices 440 maygenerate blocks for the blockchain(s), interact with smart contractsrelated to and/or implemented on the blockchain(s) of blockchain network200, request transaction information, and/or request marketing data foruse by the third party.

The automated event processing computing platform 410 may furtherconnect to the one or more user computing devices 420. The usercomputing devices 420 may be customers of services provided theautomated event processing computing platform 410. For example, theusers associated with the user computing devices 420 may maintainaccounts and credentials for services offered by the automated eventprocessing computing platform 410. Additionally or alternatively, theusers of user computing devices 420 may be users who wish to interactwith (e.g., perform a transaction with) customers of services providedby the automated event processing computing platform 410.

The automated event processing computing platform 410 may furtherconnect to one or more event information source(s) 430, from which theautomated event processing computing platform 410 may receiveinformation about events related to the users of the user computingdevices 420. For example, the event information source(s) 430 mayprovide information about transactions related to a user (e.g., creditcard purchases of the user, other payments from or to the user, and thelike), background information about a user (e.g., demographicsinformation, educational information, background check information,financial records, credit reports, and the like), and other suchinformation about the user. In some cases, a user of user computingdevice 420 may provide authorization to the automated event processingcomputing platform 410 and/or event information source(s) 430 before theautomated event processing computing platform 410 receives eventinformation from the event information sources 430. Additionally oralternatively, the automated event processing computing platform 410 mayreceive event information directly from the user (e.g., informationabout a cash purchase to or from the user, a smart contract created byor used by the user, and the like).

After receiving event information from the event information source(s)430 and/or the user computing devices 420, the automated eventprocessing computing platform 410 may analyze the various eventinformation to generate trust information for the user. The automatedevent processing computing platform 410 may further execute functionsrelated to smart contracts involving the user (which mayprogrammatically leverage the trust information), provide the trustinformation to the user or other parties, provide proofs of payment, andprovide marketing data, among other functions. The automated eventprocessing computing platform 410 may execute the method of FIGS. 5A-5Fto perform these and other functions.

FIGS. 5A-5F depict an example method by which the automated eventprocessing computing platform 410 may perform functions describedherein. Turning to FIG. 5A, at step 501, the automated event processingcomputing platform 410 may receive user authorization to access eventinformation. A user may thus designate an institution (e.g., a financialinstitution) associated with the automated event processing computingplatform 410 as a custodian of the user's event information (and byextension, as a custodian of one or more user blockchains containing theauthorized event information, as further discussed below). For example,a user may log into a portal provided by the automated event processingcomputing platform 410 and provide authorization for the automated eventprocessing computing platform 410 to receive event information from oneor more event information sources 430. An example of such a userauthorization portal is depicted at FIGS. 6A-6B. FIG. 6A illustrates ascreen 600 generated by the automated event processing computingplatform 410 and transmitted to a user computing device 420 (e.g., as aweb page) during a sign-up process. In the illustrated example, theautomated event processing computing platform 410 may require a user toconsent to running a background check including a credit report todiscover accounts and credit history associated with the user. In otherexamples, the user may provide such information without having to run acredit report and/or the automated event processing computing platform410 may obtain the required information from some other source.

FIG. 6B illustrates another screen 650 generated by the automated eventprocessing computing platform 410 and transmitted to a user computingdevice 420 (e.g., as a web page) during the sign-up process. In theillustrated example, the user may provide authorization credentials forone or more user accounts so that the automated event processingcomputing platform 410 may access computing devices (e.g., eventinformation sources 430) associated with each account in order toretrieve event information associated with the user. Additionally oralternatively, the user may directly connect to event informationsources 430 and instruct one or more of the event information sources430 to transmit event information for the user to the automated eventprocessing computing platform 410.

The automated event processing computing platform 410 may require theuser to provide access and/or authorization for some (as illustrated) orall of the user's accounts. For example, the automated event processingcomputing platform 410 may require the user to provide access to eachaccount of a first type (e.g., revolving debt accounts, checkingaccounts, and the like) in order to complete a sign-up process and mayprovide the user with incentives (e.g., reduced fees, reducedadvertising, additional services, blockchain tokens, and the like) toprovide access to additional accounts of a second type. As anotherexample, the automated event processing computing platform 410 mayprovide the user with additional incentives for each additional accountfor which the user provides access and/or authorization. Such incentivesmay include a certain number of blockchain tokens based on the number ofaccounts the user adds and/or an agreement to provide the user a certainnumber of blockchain tokens for each event associated with the user thatis added onto the blockchain(s).

In some cases, the automated event computing platform 410 may alsoreceive additional information (e.g., for users with limited financialor credit records). Users may provide access to school records,standardized test scores, mobile phone accounts and/or paymenthistories, and other such information. The user may upload suchinformation (e.g., copies of report cards, transcripts, phone bills, andthe like) and/or provide credentials so that automated event computingplatform 410 may retrieve such information from event informationsources 430. In some cases, automated event computing platform 410 mayonly consider such information if it detects that the user has limitedcredit history (e.g., less than a threshold number of financial accountsor under a threshold amount of debt).

The automated event processing computing platform 410 may be configuredto not require the user to provide authorization and/or access to someor all of the event information sources 430. For example, the automatedevent processing computing platform 410 may be owned and/or maintainedby a financial institution that also maintains one or more user accounts(e.g., a credit card and/or checking accounts), so the automated eventprocessing computing platform 410 may already have access to events forthose particular user accounts.

After completing step 501, the automated event processing computingplatform 410 may be able to access event information associated with theuser from the one or more event information sources 430. Accordingly, atstep 502, the automated event processing computing platform 410 may sendperiodic requests to the one or more event information sources 430 andresponsively receive event information therefrom. Additionally oralternatively, some or all of the event information sources 430 mayproactively push the event information (e.g., upon occurrence of arelevant transaction) to the automated event processing computingplatform 410.

At step 503, the automated event processing computing platform 410 maymatch the received event(s) that are associated with a particular userto a corresponding blockchain identifier. One or more of the blockchains200 implemented by the blockchain network 200 may use a persistentblockchain identifier to store information associated with a particularuser. The automated event processing computing platform 410 may storesuch a blockchain identifier in an identity database 415, as illustratedat FIG. 4. The identity database 415 may contain the blockchainidentifier as well as other identifiers of the user (e.g., a name of theuser, account username(s) and/or numbers of the user, and other useridentity information). When the automated event processing computingplatform 410 receives event information, the event information mayindicate that an event is associated with a user identifier, which theautomated event processing computing platform 410 may extract and use toretrieve the matching blockchain identifier for the user from theidentity database 415. Additionally, if the event includes multipleparties (e.g., a counterparty to a transaction), the automated eventprocessing computing platform 410 may also extract the other partyidentifiers and determine corresponding blockchain identifiers.

At step 504, the automated event processing computing platform 410 mayretrieve historical event information associated with the user. Thehistorical event information may be stored on one or more blockchains ofthe blockchain network 200. In some examples, each user may beassociated with a user blockchain, which may be identified by the user'sblockchain identifier. The automated event processing computing platform410 may access the user blockchain, which may be stored in memory 220 ofthe full node computing device 210 that is part of the automated eventprocessing computing platform 410 (and/or in memory 260 that is part ofthe lightweight node computing device 250 that is part of the automatedevent processing computing platform 410) and access the historical eventinformation stored on the user blockchain. The automated eventprocessing computing platform 410 may access all of the historical eventinformation starting from the beginning of the blockchain and/or mayaccess only some of the historical event information (e.g., the mostrecent 7 years). In some cases, the automated event processing computingplatform 410 may ignore (e.g., not access or filter out from theaccessed information) historical event information stored in blocks thathave timestamps earlier than a threshold date (e.g., 7 years in thepast).

In some cases, a user blockchain may be partially or wholly stored onanother full node 210 (e.g., not every full node 210 of the blockchainnetwork 200 may store each user blockchain or the entirety of each userblockchain). Accordingly, if the automated event processing computingplatform 410 does not have all or part of the user blockchain containingthe historical event information for the user, the automated eventprocessing computing platform 410 may request the relevant userblockchain (e.g., by sending a request for a user blockchain associatedwith the user's blockchain identifier) from another full node 210 of theblockchain network 200 that does have such information.

The user blockchains may be sidechains that relate to a main chaincontaining the trust information. In other words, a main chain mayinclude trust information for the users, and one or more othersidechains may include the event information for some or all of theusers. In this example, the automated event processing computingplatform 410 may regularly add received event information to the one ormore side chains and periodically update the trust information on themain chain.

Turning to FIG. 5B, at step 505 the automated event processing computingplatform 410 may generate user trust information based on the receivedevent information and the historical event information retrieved at step504. The automated event processing computing platform 410 may use oneor more models to generate the trust information using the eventinformation (e.g., the received event information and the historicalevent information) as an input. The one or more models may be trained bythe automated event processing computing platform 410 using machinelearning and/or statistical techniques.

For example, prior to executing the method of FIGS. 5A-5F, the automatedevent processing computing platform 410 may have trained a model tooutput trust information using a training data set comprising eventinformation for a large number of users and one or more targetvariables. The event information may include transaction information,which may indicate an asset that was exchanged, a value of the asset,whether the corresponding user in the training data set was a buyer orseller of the asset, a time of the asset exchange, a location of thecorresponding user at the time of the asset exchange, as well as similarsuch information for the transaction counterparty. The event informationmay further include background information for the corresponding user ofthe training data set, such as education level, place of residence,background, credit history, and other such information about thecorresponding user. The one or more target variables may indicate, forexample, whether the corresponding user in the training data set madepayments on a loan obligation, performed or failed to perform part of acontract, or other evidence of high or low financial trustworthiness.The automated event processing computing platform 410 thus may train theone or more models using the training data set to output trustinformation (e.g., by developing a neural network that maps the inputdata to the one or more target variables).

The trained model(s) may tend to indicate higher or lower levels oftrust based on the event information (including transaction informationand user information) and associated data. For example, the trainedmodel may tend to indicate a lower level of trust if the historicalevent information indicates a high amount of spending and a low amountof income. As another example, the trained model may tend to indicate alower level of trust if the user makes several large transactions incertain locations (e.g., Las Vegas) as opposed to other locations. Asanother example, the trained model may tend to indicate a higher levelof trust based on certain user information (e.g., a high level ofeducation, an older age) or a lower level of trust based on other userinformation (e.g., negative items on a background check). Accordingly,the model may determine trust information based on the inputted eventinformation. The trust information may be a continuous numerical value(e.g., a score within a range) and/or a discrete category. For example,discrete categories may include a range (e.g., from trust category 1 upto trust category 5) and/or clusters (e.g., demographic and/orbehavioral clusters such as a cluster for high income earners, a clusterfor frugal spenders, a cluster for frequent gamblers, and the like).

The automated event processing computing platform 410 may avoidexecuting step 505 to generate trust information each time a new eventis received for a user. For example, the automated event processingcomputing platform 410 may check a timestamp associated with the mostrecent generated trust information (which may be stored in a block 227of a main blockchain 226 of the blockchain network 200), and generatetrust information if the timestamp is older than a certain thresholdperiod of time. As another example, the automated event processingcomputing platform 410 may determine that a certain threshold number ofevents have been stored on a blockchain (e.g., a side blockchaincontaining user event information) since the last trust information wasgenerated, and responsively generate updated trust information.

Returning to FIG. 5B, at step 506, after generating the trustinformation by inputting the received event information and historicalevent information into the trained model to output the user trustinformation, the automated event processing computing platform 410 maygenerate an event record containing information about the received eventand/or the generated trust information. The automated event processingcomputing platform 410 may create the event record and, if the eventrepresents a transaction, populate it with transaction information suchas the seller of an asset (e.g., the blockchain identifier of the userif the user is the seller, or of the counterparty if the counterparty isthe seller), the buyer of an asset, any other parties involved in thetransaction, and an amount of the asset. As another example, if theevent involves new or changed user information (e.g., a new address, anew job, a new credit card account, and the like), the automated eventprocessing computing platform 410 may populate the event record withrelevant information such as the identifier of the associated user(e.g., the blockchain identifier), the new or changed information, and aparty that reported the new or changed information (e.g., using ablockchain identifier of the reporting party).

In some cases, the event record may also include the trust information.The automated event processing computing platform 410 may thus includetrust information in the blockchain together with the event information.Additionally or alternatively, the trust information may be stored onone blockchain (e.g., a main chain) and the event information may bestored on another blockchain (e.g., a sidechain). For events involvingtwo or more parties (e.g., transactions from one party to anotherparty), events may be generated for different blockchains correspondingto each party. For example, the automated event processing computingplatform 410 may generate records for both a seller associated with afirst user blockchain and a buyer associated with a second userblockchain, Therefore, at step 506 the automated event processingcomputing platform 410 may generate two or more event records (one foreach blockchain on which the event and/or trust information will bestored).

At step 507, the automated event processing computing platform 410 maygenerate one or more new blocks containing several event recordsassociated with a plurality of events (e.g., after receiving eventinformation for a plurality of transactions related to a plurality ofusers). It should be understood that steps 501-506 could be repeated(e.g., sequentially or in batches) for a plurality of events related toa plurality of users before generating a new block comprising eventrecords for the plurality of events. Therefore, the generated new blockmay comprise a large number of event records. The event records mayinclude event information and/or trust information, as well as othertypes of data for storage on the blockchain, such as smart contracts,which will be further discussed below.

If the automated event processing computing platform 410 generates eventrecords for more than one blockchain (e.g., a main chain and one or moreside chains), the automated event processing computing platform 410 mayrepeat step 507 to generate the new blocks for the multiple blockchains.

In some cases (e.g., for a public blockchain), the automated eventprocessing computing platform 410 may be required to solve a difficultmathematical problem (e.g., if the blockchain network 200 uses a proofof work consensus algorithm) or otherwise demonstrate entitlement togenerate the new block before generating the new block. Consensusalgorithms are described in more detail above in the “ComputingArchitectures” section. In other cases (e.g., for a permissionedblockchain), the automated event processing computing platform 410 maybe a trusted node and therefore may not need to demonstrate entitlementto generate the new block in accordance with a consensus algorithm.

When the automated event processing computing platform 410 successfullygenerates a new block, it may receive tokens associated with theblockchain as a reward for contributing to the blockchain by mutualagreement of all the nodes of the blockchain network 200. The automatedevent processing computing platform 410 may be required to share some ofthe tokens with the users associated with the events and/or trustinformation of the new block. The users may thus receive tokens as anincentive to store their associated event and/or trust information onthe blockchain(s).

At step 508, the automated event processing computing platform 410 maytransmit the generated new block(s) to the other full nodes 210 of theblockchain network 200. Each full node 210 may verify the new block andadd the new block to the blockchain, and the blockchain will continuegrowing therefrom.

Turning to FIG. 5C, at step 509, the automated event processingcomputing platform 410 may receive a request (e.g., from a user or alightweight node 250) to initialize a smart contract. The smart contractmay contain executable instructions that may be placed on the blockchain(e.g., in an event record of a new block). The smart contract mayinclude an initialization function that the automated event processingcomputing platform 410 may execute before placing the initialized smartcontract on the blockchain. For example, the initialization function maycreate data structures, populate variables, and create other such datafor use by the smart contract. Thus, a new event record containing thesmart contract may contain executable code as well as associated data.

Initializing a smart contract may require the requesting user to pay acertain amount of blockchain tokens (e.g., to the automated eventprocessing computing platform 410 for initializing the smart contract).The amount may vary based on the complexity of the smart contract and/orthe initialization function (e.g., how much processing power is requiredto execute the smart contract and/or initialization function).Additionally or alternatively, the amount may vary based on the lengthof the smart contract and associated data (e.g., in bytes). Thelightweight nodes 250 may obtain tokens from users (e.g., usingincentives as discussed above) or otherwise purchase tokens so that theymay pay the required amount of tokens to initialize and/or execute thesmart contract. Similarly, users that do not have sufficient tokens toexecute or initialize a smart contract may purchase the tokens (e.g. ona token exchange or from another user) before sending a request.

At step 510, the automated event processing computing platform 410 mayagain generate and transmit a new block containing event recordsincluding an event record containing the (initialized) smart contract.As discussed above for steps 507-508, the new block may contain aplurality of other event records for various events (e.g., transactions,user information, other smart contracts, and the like), and theautomated event processing computing platform 410 may transmit the newblock to the other nodes on the blockchain network 200.

At step 511, the automated event processing computing platform 410 mayreceive a request to execute a function of the smart contract. Therequest may be received from any party; however, the smart contract mayspecify which parties are allowed to invoke certain functions. Somefunctions may only be accessed by the user that created the smartcontract. For example, a user may create a smart contract to purchasegoods containing a function that allows the user to designate the goodsas satisfactory quality before the user's payment is released to theseller. Accordingly, the request may contain a value that the functionof the smart contract may use to execute conditional or other logic. Asanother example, the smart contract may have a function to cancel thesmart contract that only the creator may access.

Some functions may be accessed by potential counterparties. For example,a user looking for a loan may create a smart contract to allow potentiallenders to bid on a loan to the user. The potential bidders may access asmart contract function for offering a particular amount and/or interestrate. The potential counterparties may send the request to execute thefunction via a user computing device 420 (e.g., if another user isbidding on the loan) and/or via third party computing devices 440 (e.g.,if a financial institution is bidding on the loan). Accordingly, therequest may contain multiple values (e.g., an interest rate, a loanamount, and the like) that the smart contract may use and/or store. Sucha bidding function may be configured to receive multiple offers beforedeciding (e.g., automatically and/or based on user input) which offer(s)to accept.

The request to perform the smart contract function may specify a smartcontract address and the function to be executed. Based on the smartcontract address, the automated event processing computing platform 410may identify a block of the blockchain that stores the smart contract,retrieve the identified block, and extract the smart contract. Theautomated event processing computing platform 410 may also requirepayment of a certain amount of blockchain tokens for executing the smartcontract function. Therefore, the function request may also include atoken payment to a blockchain address associated with the automatedevent processing computing platform 410.

The request to perform the smart contract function may further includean authorization to execute the smart contract function. For example,the request may include data signed by the private key of the user thatcreated the function in order to demonstrate the user's authorization.In this way, the user may control who is able to access the functions ofthe smart contract by selectively providing authorization (e.g., bysigning their requests) to parties that wish to execute smart contractfunctions. Additionally or alternatively, the user may allow somefunctions to be executed by anyone (e.g., without authorization).

The smart contract may beneficially access the user trust informationstored on the blockchain. For example, a function of the smart contract(including an initialization function or any other function) mayconditionally execute a function based on a value of the trustinformation for a user or a counterparty. Thus a function of the smartcontract may only execute if a user or counterparty is associated with asufficiently high level of trust and/or if the user or counterpartyfalls into one of a subset of discrete trust categories. For example, asmart contract for a loan may require reduced collateral and/or areduced interest rate if the loanee has qualifying (e.g., over a firstthreshold value) trust information. Additionally or alternatively, theloan smart contract may only allow loans to be made to loanees withsufficiently high (e.g., over a second threshold value) trustinformation. In the loan example, the second threshold value may belower than the first threshold value.

Therefore, at step 512, the automated event processing computingplatform 410 may retrieve trust information for one or more parties ofthe contract as needed before executing the requested function. If theautomated event processing computing platform 410 does not have accessto trust information (e.g., if the automated event processing computingplatform 410 implements a lightweight node 250 that does not store anentire blockchain), the automated event processing computing platform410 may request the trust information from other nodes on the blockchainnetwork 200 by sending a request to another node to retrieve trustinformation associated with a blockchain identifier. The other node mayrespond with one or more relevant blocks 227, which the automated eventprocessing computing platform 410 may verify before extracting the trustinformation.

Turning to FIG. 5D, at step 513, the automated event processingcomputing platform 410 may execute the smart contract function.Execution of some functions may require updating the blockchain (e.g.,in order to store data generated or changed during the execution of thefunction). For example, if the function receives a loan bid from apotential lender, the function may require an update in order to storethe bid on the blockchain. Execution of other functions may not requireany blockchain update. For example, some functions may allow users toread or view data previously generated or stored by the smart contract.

At step 514, if the function causes data to be generated and/ormodified, a new event record storing the updated state of the smartcontract may be generated. The event record may store any updated datastructures and/or other data that was changed by executing the smartcontract function.

At step 515, the automated event processing computing platform 410 mayagain generate and transmit a new block containing event recordsincluding the event record with the updated smart contract information.As discussed above for steps 507-508, the new block may contain aplurality of other event records for various events (e.g., transactions,user information, other smart contracts, and the like), and theautomated event processing computing platform 410 may transmit the newblock to the other nodes on the blockchain network 200.

At step 516, the automated event processing computing platform 410 mayreceive a request for transaction information. A user (or some otherparty) may seek information about a transaction that was placed on ablockchain. The request may identify the event record associated withthe transaction if known. Additionally or alternatively, the request mayidentify the parties to the transaction, the amount of the transaction,the time of transaction, or provide some other criteria for finding thetransaction.

The automated event processing computing platform 410 may use thecriteria to find one or more transactions matching the criteria bysearching the transactions on the one or more blockchains. In examplesthat use multiple blockchains, identity information for the user and/orcounterparty may be used to lookup corresponding blockchainidentifier(s) (e.g., as discussed above for step 503), which may be usedto select a particular blockchain (e.g., a particular user side chain)to search for the transaction.

Turning to FIG. 5E, at step 517, the automated event processingcomputing platform 410 may provide transaction information from the oneor more event records that match the criteria. The automated eventprocessing computing platform 410 may send the requested transactioninformation to whichever device requested the transaction informationand/or the automated event processing computing platform 410 may sendthe requested transaction information to some other device as requestedby the requester. For example, a first user may request that theautomated event processing computing platform 410 send transactioninformation to a second user in order to resolve a payment disputebetween the first user and the second user.

The automated event processing computing platform 410 may providelimited information about the transaction unless the requesterdemonstrates privileges to access additional information. For example,the automated event processing computing platform 410 may (by default)provide proof that a transaction was made from one (pseudonymous)blockchain identifier to another. However, if the requester is a userinvolved in the transaction or can otherwise demonstrate authorizationof the user (e.g., if the request includes data signed by a private keyof the user), the automated event processing computing platform 410 mayprovide additional information such as the user's name or otheridentifying information, which the automated event processing computingplatform 410 may obtain from the ID database 415.

At step 518, the automated event processing computing platform 410 mayreceive a trust information request from a user or some other party. Therequest may comprise an identifier of a user for which trust informationis sought. In some cases, the request may also comprise credentials(e.g., an authorization signed by the user's private key) demonstratingthat the user associated with the trust information has consented toaccess of the trust information. In this way, a user may control who mayreceive access to the user's trust information. In some cases, thecredentials may allow access to the user's trust information for alimited time. Therefore, a user may control who may access the trustinformation and for how long. Accordingly, the automated eventprocessing computing platform 410 may verify the credentials provided inthe request, and reject the request if the credentials are invalidand/or expired. Additionally or alternatively, the user may allow anyparty to access the trust information (e.g., if the user is interestedin unsolicited offers). A user may use a portal (e.g., a web portalsimilar to the portal illustrated at FIGS. 6A-6B) to log into theautomated event processing computing platform 410 and configure theaccess settings in order to configure who may access the trustinformation.

The automated event processing computing platform 410 may responsivelydetermine a blockchain identifier for the user (if the identifier in therequest is not the blockchain identifier) and locate trust informationfor the identified user (e.g., the most recently generated trustinformation). Then, at step 519, the trust information may be sent tothe requesting device. Thus, the trust information may be used for smartcontracts or other transactions that take place off the one or moreblockchains of the blockchain network.

At step 520, the automated event processing computing platform 410 mayreceive a request for marketing data. The automated event processingcomputing platform 410 may generate anonymized and/or aggregatedmarketing data from the event information stored on the blockchain. Suchmarketing data may be stored in marketing database 416. For example, theautomated event processing computing platform 410 may generate dataindicating what types of purchases are made by certain demographicand/or trust market segments (e.g., preferred products, preferredstores, and the like for certain demographic groups and/or groupsassociated with certain trust information). The marketing data mayinclude trends such as increases or decreases in certain types ofpurchases for certain demographic and/or trust market segments, andother such data about purchasing habits and how they change over time.The marketing data trust segments may be defined to include certainranges (e.g., a segment for all users with trust information over afirst threshold, another segment for users with trust information belowthe first threshold but above a second threshold, and the like) orclusters of trust information.

The automated event processing computing platform 410 may requirepayment of tokens in exchange for marketing data. As discussed above,tokens may be provided to nodes that participate in the blockchainnetwork 200 as full nodes 210 by generating new blocks. Accordingly,third parties that desire marketing data may be incentivized toparticipate in the blockchain network 200. Additionally oralternatively, tokens may be provided to users that choose to supplyevent information from event information sources 430. Other thirdparties that desire marketing data (e.g., third parties associated withlightweight nodes 250) may provide incentives for users to transfertheir tokens to the third parties so that the third party may use thetokens to purchase marketing data. For example, a third party mayprovide a discount, rebate, or other award to a user that transferstokens to the third party. Another third party may offer loyalty points(e.g., airline miles or credit card points) to a user that transferstokens to it. Thus, users and/or third parties may be incentivized toparticipate in the blockchain network 200.

Turning to FIG. 5F, at step 521, the automated event processingcomputing platform 410 may provide the marketing data to the requestingdevice. The automated event processing computing platform 410 mayprovide an amount of marketing data commensurate with the payment oftokens from the requesting device. As discussed above, the providedmarketing data may be anonymized (e.g., stripped of user identifiers)and/or aggregated (e.g., compiled into aggregate statistics).

At step 522, the automated event processing computing platform 410 mayperiodically update its training data set to include all or some of theevent information received since the last time the trust models wereupdated. The automated event processing computing platform 410 may thenproceed to retrain the one or more trust models based on the updatedtraining data.

The process of FIGS. 5A-5F may repeat periodically, and some of thesteps may repeat in different orders. For example, as discussed above,step 501 may repeat whenever a new user agrees to provide eventinformation from one or more accounts. Steps 502-506 may repeatperiodically and/or based on the receipt of event information by theautomated event processing computing platform 410. Steps 507-508 mayrepeat at certain intervals set by the blockchain network and/orwhenever the full node 210 of the automated event processing computingplatform 410 is able to generate a new block (e.g., after finding a hashfor a proof of work consensus algorithm). Steps 509-510 may repeatwhenever the automated event processing computing platform 410 receivesa request to initialize a smart contract. Steps 511-513 may repeatwhenever the automated event processing computing platform 410 receivesa request to execute a smart contract function. Steps 514-515, likesteps 507-508, may repeat at certain intervals set by the blockchainnetwork and/or whenever the full node 210 of the automated eventprocessing computing platform 410 is able to generate a new block. Steps516-517 may repeat whenever the automated event processing computingplatform 410 receives a request for transaction information. Steps518-519 may repeat whenever the automated event processing computingplatform 410 receives a request for trust information. Steps 520-521 mayrepeat whenever the automated event processing computing platform 410receives a request for marketing information. And step 522 may repeatperiodically, among other variations.

FIG. 7 depicts an illustrative system and operating environment forimplementing additional features of the present disclosure. In thesystem of FIG. 7, an automated event processing computing platform 710may interact with one or more corporate entity computing devices 720,which may further interact with each other according to various supplychains. For example, corporations associated with the various corporateentity computing devices 720 may buy and sell goods and services fromand to the other corporations. Some or all of the corporate entitycomputing devices 720 may provide information about the transactions andsupply chains to the automated event processing computing platform 710.

The automated event processing computing platform 710 may connect to ablockchain network, such as blockchain network 200. The blockchainnetwork 200 may be a permissioned blockchain network created by ablockchain consortium (e.g., a consortium of organizations that providefinancial or related services to corporations). Information about thetransactions and corporate supply chains may be stored on the blockchainin encrypted form and/or access to the blockchain may be restricted suchthat the information is not made public.

The automated event processing computing platform 710 may implement anode of the blockchain network, such as a full node 210 such that theautomated event processing computing platform 710 may participate in theone or more blockchains of the blockchain network 200. The automatedevent processing computing platform 710 may implement the node as aphysical device that makes up part of the automated event processingcomputing platform 710 and/or may implement the node as a virtualizeddevice and/or software module running inside hardware of the automatedevent processing computing platform 710. In some examples, the automatedevent processing computing platform 710 may implement multiple (e.g.,virtualized) nodes that interact with multiple blockchains (e.g., oneblockchain per node) on the same blockchain network 200 and/or differentblockchain networks.

FIGS. 8A-8E depict an example method by which the automated eventprocessing computing platform 710 may perform functions describedherein, including generating and maintaining a blockchain containingtrust information for corporate entities. Turning to FIG. 8A, at step801, the automated event processing computing platform 710 may receiveintegration configuration information for accessing event and supplychain information for the corporation. For example, the corporation mayexpose APIs for the automated event processing computing platform 710 tosecurely access its internal event and supply chain information (whichmay be available from a corporate entity computing device 720), such asinformation about past, current, and future supply chains, informationabout other transactions for the corporation, and other such informationabout asset flows to and from the corporation. Thus, the integrationconfiguration information may include information about how to accessthe API (e.g., how to format API requests) as well as credentialinformation for securely accessing the API. API requests received fromthe corporate entity computing device 720 may include a blockchainidentifier for the corporation. Other methods of integrating with thecorporate records may be used as well. For example, the corporation mayconfigure its internal systems to periodically push the relevantinformation to the automated event processing computing platform 710.The pushed information may include a blockchain identifier for thecorporation.

In some cases, the automated event processing computing platform 710 maybe affiliated with (e.g., part of or located inside the corporatenetwork of) the corporation from which the event and supply chaininformation is received.

The automated event processing computing platform 710 may provideincentives to corporations for providing the supply chain and/or eventinformation. Such incentives may include providing blockchain tokensand/or providing products and services (e.g., financial products andservices) at reduced prices or interest rates.

The supply chain information may describe the relationships betweencorporate and other entities involved in delivering a good or service toone or more customers. It may describe how goods and/or services aresupplied from entity to entity in order to support and supply theprovision of a good and/or service by a particular corporate entity. Adata structure for storing the supply chain information may includecorporate or other entities as nodes of a graph, and the provision ofgoods and services between corporate or other entities as links betweennodes of the graph. Each node may be associated with information such asan identifier (e.g., of the corporate entity), a location of the entity,trust information for the entity, and other such entity information.Each link may be associated with information such as an identificationof the direction of the link (e.g., which node is the buyer and which isthe seller), an identification of the goods or services provided, anumber of goods provided, a cost of the goods or services provided, anexpected date or frequency of the goods or services provided, and othersuch information.

After completing step 801, the automated event processing computingplatform 710 may be able to access event and supply chain informationassociated with the corporation from a corporate entity computing device720. Accordingly, at step 802, the automated event processing computingplatform 710 may send periodic requests to the corporate entitycomputing device 720 and responsively receive event and supply chaininformation therefrom.

At step 803, the automated event processing computing platform 710 mayretrieve historical corporate information for the corporation from whichthe event and supply chain information was received at step 802. Suchinformation may be stored on one or more blockchains of the blockchainnetwork, and may include previous event information (e.g., previoustransactions as well as previous corporate events such asincorporations, IPOs, and other such events). In some examples,additional corporate information (e.g., country of incorporation orother background information) may be stored in and retrieved from adatabase of the automated event processing computing platform 710 (e.g.,corporate database 715).

At step 804, the automated event processing computing platform 710 mayretrieve supply chain information for other corporations involved in thesupply chains received at step 802. The other corporate supply chaininformation may be stored on one or more blockchains of the blockchainnetwork 200 and/or may be stored in a database of the automated eventprocessing computing platform 710 (e.g., in supply chain database 716).In some examples, each corporation may be associated with a corporateblockchain, which may be identified by the corporation's blockchainidentifier. The automated event processing computing platform 710 mayaccess the desired corporate blockchain in order to retrieve the supplychain information therefrom. The corporate blockchain may be stored inmemory 220 of the full node computing device 210 that is part of theautomated event processing computing platform 710 (and/or in memory 260of the lightweight node computing device 250 that is part of theautomated event processing computing platform 710). The automated eventprocessing computing platform 710 may repeat this process to collectsupply chain information for each of the corporations involved with thesupply chain received at step 802. If supply chain information for theother corporation is not stored on the blockchain, the automated eventprocessing computing platform 710 may send a request to a corporateentity computing device 720 seeking information about the corporationand/or its supply chains that involve the corporation from which supplychain information was received at step 802.

In some cases, a corporate blockchain may be stored on another full node210 (e.g., not every full node 210 of the blockchain network 200 maystore each corporate blockchain or the entirety of each corporateblockchain). Accordingly, if the automated event processing computingplatform 710 does not have all or part of the corporate blockchainsneeded for steps 803 or 804, the automated event processing computingplatform 710 may request the relevant corporate blockchain (e.g., bysending a request for a corporate blockchain associated with thecorporation's blockchain identifier) from another full node 210 of theblockchain network 200 that does have such information.

The corporate blockchains may be sidechains that relate to a main chaincontaining the trust information for the corporations. In other words, amain chain may include trust information for the corporations, and oneor more other sidechains may include the event and supply chaininformation for some or all of the corporations. In this example, theautomated event processing computing platform 710 may regularly addreceived event and supply chain information to the one or more sidechains and periodically update the trust information on the main chain.

Turning to FIG. 8B, at step 805, the automated event processingcomputing platform 710 may generate corporate trust information based onthe received event and supply information, the historical corporateinformation received at step 803, and the other corporation supply chaininformation retrieved at step 804. The automated event processingcomputing platform 710 may use one or more models to generate the trustinformation using the received event and supply chain information, thehistorical corporate information, and other corporation supply chaininformation as an input. The one or more models may be trained by theautomated event processing computing platform 710 using machine learningand/or statistical techniques.

For example, prior to executing the method of FIGS. 8A-8E, the automatedevent processing computing platform 710 may have trained a model tooutput trust information using a training data set comprising corporateinformation for a large number of corporations and one or more targetvariables. The corporate information may include transactioninformation, which may indicate an asset that was exchanged, a value ofthe asset, whether the corresponding corporation in the training dataset was a buyer or seller of the asset, a time of the asset exchange, aswell as similar such information for the transaction counterparty. Thecorporate information may further include supply chain information, suchas regular and/or planned asset purchases or sales to othercorporations, the amount of planned assets purchases or sales,identifiers of each of the corporations involved in the supply chains,trust information associated with each of the corporations involved inthe supply chains, and the like. The corporate information may furtherinclude background information for the corresponding corporation of thetraining data set, such as corporate history, state or country ofincorporation, credit rating of the corporation, and other suchinformation about the corresponding corporation. The one or more targetvariables may indicate, for example, whether the correspondingcorporation in the training data set made payments on a loan obligation,performed or failed to perform part of a contract, or other evidence ofhigh or low trustworthiness. The automated event processing computingplatform 710 thus may train the one or more models using the trainingdata set to output trust information (e.g., by developing a neuralnetwork that maps the input data to the one or more target variables).

The automated event processing computing platform 710 may also havetrained the model (or a separate model) to generate trust informationbased on a comparison of supply chain information related to variouscorporate entities. For example, such a model may be trained torecognize discrepancies between supply chain information received from afirst company that relates to a second company and supply chaininformation received from a second company that related to a firstcompany. Such discrepancies may indicate a lack of accurate bookkeepingor otherwise indicate low trustworthiness.

The trained model(s) may tend to indicate higher or lower levels oftrust based on the corporation information (including event and supplychain information) and associated data. For example, the trained modelmay tend to indicate a lower level of trust if a corporation's supplychains involve other corporations with low trust information. In thisexample, the model may be trained to provider greater or lesser weightto low corporate trust information based on a relative position in thesupply chain. For example, low trust suppliers upstream of the corporateentity may be weighted more heavily than low trust buyers downstream ofthe corporate entity. Additionally or alternatively, the trained modelmay tend to indicate a lower level of trust if the corporation isincorporated in certain countries (e.g., with undeveloped legal systems)as opposed to other countries. Additionally or alternatively, thetrained model may tend to indicate a higher level of trust based oncertain corporate information (e.g., a long history since incorporation,a low indebtedness) or a lower level of trust based on other corporateinformation (e.g., a pending lawsuit against the corporation).Additionally or alternatively, the trained model may tend to indicate alower level of trust based on discrepancies between supply chaininformation for the various corporations, as discussed above.Accordingly, the model may determine trust information based on theinputted event and supply chain information. The trust information maybe a continuous numerical value (e.g., a score within a range) and/or adiscrete category. For example, discrete categories may include a rangefrom trust category 1 up to trust category 5.

The automated event processing computing platform 710 may avoidexecuting step 805 to generate trust information each time new event andsupply chain information is received for a corporation. For example, theautomated event processing computing platform 710 may check a timestampassociated with the most recent generated trust information (which maybe stored in a block 227 of a main blockchain 226 of the blockchainnetwork 200), and generate trust information if the timestamp is olderthan a certain threshold period of time. As another example, theautomated event processing computing platform 710 may determine that acertain threshold number of events have been stored on a blockchain(e.g., a side blockchain containing corporate information) since thelast trust information was generated, and responsively generate updatedtrust information.

At step 806, after generating the trust information by inputting thereceived event and supply chain information and historical corporateinformation into the trained model to output the user trust information,the automated event processing computing platform 710 may generate anevent record containing information about the received event and supplychain information and/or the generated trust information. The automatedevent processing computing platform 710 may create the event record and,if the event represents a transaction, populate it with transactioninformation such as the seller of an asset (e.g., the blockchainidentifier of the corporation if the corporation is the seller, or ofthe counterparty if the counterparty is the seller), the buyer of anasset, any other parties involved in the transaction, and an amount ofthe asset. As another example, if the event involves supply chaininformation (e.g., listings of buyers and sellers of assets to and fromthe corporation, as well as transactions taking place upstream ordownstream of the corporation), the automated event processing computingplatform 710 may populate the event record with relevant informationsuch as the identifiers of the associated corporations (e.g., theblockchain identifiers) and the planned asset sales and purchasesthroughout the supply chain.

In some cases, the event record may also include the trust information.The automated event processing computing platform 710 may thus includetrust information in the blockchain together with the event information.Additionally or alternatively, the trust information may be stored onone blockchain (e.g., a main chain) and the event information may bestored on another blockchain (e.g., a sidechain). For events involvingtwo or more parties (e.g., transactions from one party to anotherparty), events may be generated for different blockchains correspondingto each party. For example, the automated event processing computingplatform 710 may generate records for both a seller associated with afirst corporate blockchain and a buyer associated with a secondcorporate blockchain. Additionally or alternatively, the automated eventprocessing computing platform 710 may generate an event record for eachcorporation involved in a corporate supply chain. Therefore, at step 806the automated event processing computing platform 710 may generate twoor more event records (one for each blockchain on which the event andsupply chain information and/or trust information will be stored).

At step 807, the automated event processing computing platform 710 maygenerate one or more new blocks containing several event recordsassociated with various event and supply chain information (e.g., afterreceiving a plurality of event and supply chain information). It shouldbe understood that steps 801-806 could be repeated (e.g., sequentiallyor in batches) for a plurality of such information related to aplurality of corporations before generating a new block comprising eventrecords for the various information. Therefore, the generated new blockmay comprise a large number of event records.

If the automated event processing computing platform 710 generates eventrecords for more than one blockchain (e.g., a main chain and one or moreside chains), the automated event processing computing platform 710 mayrepeat step 807 to generate the new blocks for the multiple blockchains.The automated event processing computing platform 710 may implement atrusted node (e.g., for a permissioned blockchain network) and thereforemay not need to demonstrate entitlement to generate the new block inaccordance with a consensus algorithm.

When the automated event processing computing platform 710 successfullygenerates a new block, it may award blockchain tokens to thecorporations associated with the event and supply chain information ofthe new block. The corporations may thus receive tokens as an incentiveto store their associated event and supply chain information on theblockchain(s), and to allow trust information to be generated therefrom.

At step 808, the automated event processing computing platform 710 maytransmit the generated new block(s) to the other full nodes 210 of theblockchain network 200. Each full node 210 may verify the new block andadd the new block to the blockchain, and the blockchain will continuegrowing therefrom.

Turning to FIG. 8C, at step 809, the automated event processingcomputing platform 710 may receive a request (e.g., from a corporateentity computing device 720 or a blockchain consortium computing device740) to initialize a smart contract. The smart contract may containexecutable instructions that may be placed on the blockchain (e.g., inan event record of a new block). The smart contract may include aninitialization function that the automated event processing computingplatform 710 may execute before placing the initialized smart contracton the blockchain. For example, the initialization function may createdata structures, populate variables, and create other such data for useby the smart contract. Thus, a new event record containing the smartcontract may contain executable code as well as associated data.

Initializing a smart contract may require the requesting entity to pay acertain amount of blockchain tokens (e.g., to the automated eventprocessing computing platform 710 for initializing the smart contract).The amount may vary based on the complexity of the smart contract and/orthe initialization function (e.g., how much processing power is requiredto execute the smart contract and/or initialization function).Additionally or alternatively, the amount may vary based on the lengthof the smart contract and associated data (e.g., in bytes). Theblockchain consortium computing device 740 may obtain tokens by creatingnew blocks or otherwise purchase tokens so that it may pay the requiredamount of tokens to initialize and/or execute the smart contract.Similarly, corporations that do not have sufficient tokens to execute orinitialize a smart contract may purchase the tokens (e.g. on a tokenexchange or from another computing device) before sending a request.

At step 810, the automated event processing computing platform 710 mayagain generate and transmit a new block containing event recordsincluding an event record containing the (initialized) smart contract.As discussed above for steps 807-808, the new block may contain aplurality of other event records for various events (e.g., supply chaininformation, corporate information, other smart contracts, and thelike), and the automated event processing computing platform 710 maytransmit the new block to the other nodes on the blockchain network 200.

At step 811, the automated event processing computing platform 710 mayreceive a request to execute a function of the smart contract. Therequest may be received from any party; however, the smart contract mayspecify which parties are allowed to invoke certain functions. Somefunctions may only be accessed by the entity that created the smartcontract. For example, a corporate entity may create a smart contract topurchase goods containing a function that allows the corporate entity todesignate the goods as satisfactory quality before the corporateentity's payment is released to the seller. Accordingly, the request maycontain a value that the function of the smart contract may use toexecute conditional or other logic. As another example, the smartcontract may have a function to cancel the smart contract that only thecreator may access.

Some functions may be accessed by potential counterparties. For example,a corporate entity looking for a loan may create a smart contract toallow potential lenders to bid on a loan to the corporate entity. Thepotential bidders may access a smart contract function for offering aparticular amount and/or interest rate. The potential counterparties maysend the request to execute the function via a corporate entitycomputing device 720 (e.g., if another user is bidding on the loan)and/or via a blockchain consortium computing devices 740 (e.g., if afinancial institution is bidding on the loan). Accordingly, the requestmay contain multiple values (e.g., an interest rate, a loan amount, andthe like) that the smart contract may use and/or store. Such a biddingfunction may be configured to receive multiple offers before deciding(e.g., automatically and/or based on user input) which offer(s) toaccept.

The request to perform the smart contract function may specify a smartcontract address and the function to be executed. Based on the smartcontract address, the automated event processing computing platform 710may identify a block of the blockchain that stores the smart contract,retrieve the identified block, and extract the smart contract. Theautomated event processing computing platform 710 may also requirepayment of a certain amount of blockchain tokens for executing the smartcontract function. Therefore, the function request may also include atoken payment to a blockchain address associated with the automatedevent processing computing platform 710.

The smart contract may beneficially access the corporation trustinformation stored on the blockchain. For example, a function of thesmart contract (including an initialization function or any otherfunction) may conditionally execute a function based on a value of thetrust information for a corporate entity or a counterparty. Thus afunction of the smart contract may only execute if a corporate entity orcounterparty is associated with a sufficiently high level of trustand/or if the corporate entity or counterparty falls into one of asubset of discrete trust categories. For example, a smart contract for aloan may require reduced collateral and/or a reduced interest rate ifthe loanee has qualifying (e.g., over a first threshold value) trustinformation. Additionally or alternatively, the loan smart contract mayonly allow loans to be made to loanees with sufficiently high (e.g.,over a second threshold value) trust information. In the loan example,the second threshold value may be lower than the first threshold value.

Therefore, at step 812, the automated event processing computingplatform 710 may retrieve trust information for one or more parties ofthe contract as needed before executing the requested function. If theautomated event processing computing platform 710 does not have accessto trust information (e.g., if the automated event processing computingplatform 710 implements a lightweight node 250 that does not store anentire blockchain), the automated event processing computing platform710 may request the trust information from other nodes on the blockchainnetwork 200 by sending a request to another node to retrieve trustinformation associated with a blockchain identifier. The other node mayrespond with one or more relevant blocks 227, which the automated eventprocessing computing platform 710 may verify before extracting the trustinformation.

Turning to FIG. 8D, at step 813, the automated event processingcomputing platform 710 may execute the smart contract function.Execution of some functions may require updating the blockchain (e.g.,in order to store data generated or changed during the execution of thefunction). For example, if the function receives a loan bid from apotential lender, the function may require an update in order to storethe potential bid on the blockchain. Execution of other functions maynot require any blockchain update. For example, some functions may allowusers to read or view data previously generated or stored by the smartcontract.

At step 814, if the function causes data to be generated and/ormodified, the automated event processing computing platform 710 maygenerate a new event record storing the updated state of the smartcontract. The event record may store any updated data structures and/orother data that was changed by executing the smart contract function.

At step 815, the automated event processing computing platform 710 mayagain generate and transmit a new block containing event recordsincluding the event record with the updated smart contract information.As discussed above for steps 807-808, the new block may contain aplurality of other event records for various events (e.g., transactions,user information, other smart contracts, and the like), and theautomated event processing computing platform 710 may transmit the newblock to the other nodes on the blockchain network 200.

At step 816, the automated event processing computing platform 710 mayreceive a trust information request from a corporate entity or someother party. The request may comprise an identifier of a corporateentity for which trust information is sought. The automated eventprocessing computing platform 710 may responsively determine ablockchain identifier for the corporate entity (if the identifier in therequest is not the blockchain identifier) and locate trust informationfor the identified corporate entity (e.g., the most recent trustinformation). Turning to FIG. 8E, at step 817, the automated eventprocessing computing platform 710 may send the trust information to therequesting device. Thus, the trust information may be used for smartcontracts or other transactions that take place off the one or moreblockchains of the blockchain network.

At step 818, the automated event processing computing platform 710 mayperiodically update its training data set to include all or some of theevent information received since the last time the trust models wereupdated. The automated event processing computing platform 710 may thenproceed to retrain the one or more trust models based on the updatedtraining data.

The process of FIGS. 8A-8E may repeat periodically, and some of thesteps may repeat in different orders. For example, as discussed above,step 801 may repeat whenever a new corporation agrees to participate inthe blockchain by providing integration information to the 719. Steps802-806 may repeat periodically and/or based on the receipt of event andsupply chain information by the automated event processing computingplatform 710. Steps 807-808 may repeat at certain intervals set by theblockchain network and/or whenever the full node 210 of the automatedevent processing computing platform 710 is able to generate a new block.Steps 809-810 may repeat whenever the automated event processingcomputing platform 710 receives a request to initialize a smartcontract. Steps 811-813 may repeat whenever the automated eventprocessing computing platform 710 receives a request to execute a smartcontract function. Steps 814-815, like steps 807-808, may repeat atcertain intervals set by the blockchain network and/or whenever the fullnode 210 of the automated event processing computing platform 710 isable to generate a new block. Steps 816-817 may repeat whenever theautomated event processing computing platform 710 receives a request fortrust information. And step 818 may repeat periodically, among othervariations.

FIG. 9 illustrates an example process for executing functions based on atrust level associated with a user. At step 905, a computing platformcomprising one or more processors, memory, and a network interface mayreceive, via the network interface, information identifying a user. Atstep 910, the computing platform may retrieve, from one or more blocksof a blockchain stored in the memory, a plurality of historicalinformation associated with the user. At step 915, the computingplatform may calculate, based on the historical information associatedwith the user, a trust level associated with the user. At step 920, thecomputing platform may execute a function stored on the blockchain,wherein the function comprises conditional logic based on the trustlevel associated with the user. At step 925, the computing platform maygenerate a new block comprising a data structure including data modifiedby the executed function. At step 930, the computing platform maytransmit the new block to a plurality of nodes that maintain theblockchain.

FIG. 10 illustrates an example process for executing functions based ona trust level associated with a corporate entity. At step 1005, acomputing platform comprising one or more processors, memory, and anetwork interface may receive, via the network interface, informationabout a supply chain associated with a first corporate entity. At step1010, the computing platform may retrieve, from one or more blockchainsstored in the memory, information about a plurality of corporateentities associated with the supply chain. At step 1015, the computingplatform may calculate, based on the information about the supply chainand on the information for the plurality of corporate entities, a trustlevel associated with the first corporate entity. At step 1020, thecomputing platform may execute a function stored on the blockchain,wherein the function comprises conditional logic based on the trustlevel associated with the first corporate entity. At step 1025, thecomputing platform may generate a new block comprising a data structureincluding data modified by the executed function. At step 1030, thecomputing platform may transmit the new block to a plurality of nodesthat maintain the one or more blockchains.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A method comprising: at a computing platformcomprising one or more processors, memory, and a network interface:receiving, from a plurality of computing systems and via a networkinterface, event information associated with a user matching, based onthe event information, the event information to a blockchain identifierassociated with the user; retrieving, based on the blockchainidentifier, historical event information associated with the user from ablockchain corresponding to the blockchain identifier; calculating,based on the historical event information, a trust level associated withthe user; generating, based on the event information and the historicalinformation, an event block comprising a first data structure includingdata modified by an executed first function and a trust block comprisinga second data structure including data modified by an executed secondfunction; associating the event block to an event sidechain theblockchain and the trust block to a main chain of the blockchain.
 2. Themethod of claim 1, further comprising: receiving user authorization toaccess records maintained by one or more systems that record eventsassociated with the user; and receiving, based on the authorization toaccess the records, the historical event information.
 3. The method ofclaim 1, further comprising: determining, based on the user eventinformation, a blockchain identifier associated with the user andwherein the event block comprises the blockchain identifier.
 4. Themethod of claim 1, wherein conditional logic executed by the firstfunction and the second function executes when the trust level is abovea threshold.
 5. The method of claim 4, wherein the conditional logicadjusts a value based on the trust level.
 6. The method of claim 1,further comprising: receiving, from the user and before execution of thefirst function and the second function, a payment of a token associatedwith the blockchain.
 7. The method of claim 1, wherein the memorycomprises a plurality of user blockchains associated with a respectiveplurality of users, further comprising: generating, for a trust levelblockchain that is separate from the plurality of user blockchains, asecond new block comprising the trust level; and transmitting the secondnew block to a plurality of nodes that maintain the blockchain.
 8. Themethod of claim 1, wherein generating the new block causes the computingplatform to receive tokens associated with the blockchain.
 9. The methodof claim 1, wherein the historical information comprises electronictransaction information about transactions with other users or entities,locations of the transactions, and amounts of the transactions.
 10. Themethod of claim 9, wherein the historical information further comprisesone or more of user demographic information, user credit reportinformation, and information about user assets.
 11. The method of claim1, wherein the executed first function initializes a third function forreceiving a bid on a loan to the user.
 12. A computing platformcomprising: one or more processors; a network interface; and memorystoring instructions that, when executed by the one or more processors,cause the computing platform to: receive from a plurality of computingsystems and via a network interface, event information associated with auser match, based on the event information, the event information to ablockchain identifier associated with the user; retrieve, based on theblockchain identifier, historical event information associated with theuser from a blockchain corresponding to the blockchain identifier;calculate, based on the historical event information, a trust levelassociated with the user; generate, based on the event information andthe historical information, an event block comprising a first datastructure including data modified by an executed first function and atrust block comprising a second data structure including data modifiedby an executed second function; associate the event block to an eventsidechain the blockchain and the trust block to a main chain of theblockchain.
 13. The computing platform of claim 12, wherein theinstructions further cause the computing platform to: receive userauthorization to access records maintained by one or more systems thatrecord events associated with the user; and receive, based on theauthorization to access the records, the historical event information.14. The computing platform of claim 12, wherein the instructions furthercause the computing platform to: generate, for a main blockchain that isseparate from a plurality of user blockchains, a second new blockcomprising the trust level, wherein the memory comprises a plurality ofuser blockchains associated with a respective plurality of users; andtransmit the second new block to a plurality of nodes that maintain theblockchain.
 15. The computing platform of claim 12, wherein thehistorical information comprises electronic transaction informationabout transactions with other users or entities, locations of thetransactions, and amounts of the transactions.
 16. The computingplatform of claim 15, wherein the historical information furthercomprises one or more of user demographic information, user creditreport information, and information about user assets.
 17. One or morecomputer readable media storing instructions that, when executed by oneor more processors of a computing platform, cause the computing platformto: receive from a plurality of computing systems and via a networkinterface, event information associated with a user match, based on theevent information, the event information to a blockchain identifierassociated with the user; retrieve, based on the blockchain identifier,historical event information associated with the user from a blockchaincorresponding to the blockchain identifier; calculate, based on thehistorical event information, a trust level associated with the user;generate, based on the event information and the historical information,an event block comprising a first data structure including data modifiedby the executed first function and a trust block comprising a seconddata structure including data modified by the executed second function;associate the event block to an event sidechain the blockchain and thetrust block to a main chain of the blockchain.
 18. The one or morecomputer readable media of claim 17, wherein the instructions furthercause the computing platform to: receive user authorization to accessrecords maintained by one or more systems that record events associatedwith the user; and receive, based on the authorization to access therecords, the historical event information.
 19. The one or more computerreadable media of claim 17, wherein the instructions further cause thecomputing platform to: generate, for a main blockchain that is separatefrom a plurality of user blockchains, a second new block comprising thetrust level, wherein a memory comprises a plurality of user blockchainsassociated with a respective plurality of users; and transmit the secondnew block to the plurality of nodes that maintain the blockchain. 20.The one or more computer readable media of claim 17, wherein thehistorical information comprises electronic transaction informationabout transactions with other users or entities, locations of thetransactions, and amounts of the transactions.